Issue Resolution Time Research Articles

Calculating and Understanding the Usefulness of JIRA Developers Communities

Tools for project management and bugs or problems following have become useful for managing the event method of the Open supply package. These tools clear the communications task between developers and make certain the quantifiability of the given project. The additional data developers square measure ready to interchange, the brighter square measure the achievements, and therefore the larger is that the limit of developers keen on a change. During this paper, we tend to gift an introductory determined investigation of the companies-structure of developers in JIRA by learning some well-liked comes hosted within the repository. We tend to study however, these firms perform in terms of the given issue’s issue-resolution time. The most contributions of this work square measure the authentication of the survival of firms in developer networks, and therefore, the actual finding that the given issue’s problem resolution time isn't correlative with the importance of a developer company.

A new risk and issue management system to improve productivity, quality, and compliance in clinical trials.

ObjectiveWe present a new system to track, manage, and report on all risks and issues encountered during a clinical trial.Materials and MethodsOur solution utilizes JIRA, a popular issue and project tracking tool for software development, augmented by third-party and custom-built plugins to provide the additional functionality missing from the core product.ResultsThe new system integrates all issue types under a single tracking tool and offers a range of capabilities, including configurable issue management workflows, seamless integration with other clinical systems, extensive history, reporting, and trending, and an intuitive web interface.Discussion and ConclusionBy preserving the linkage between risks, issues, actions, decisions, and outcomes, the system allows study teams to assess the impact and effectiveness of their risk management strategies and present a coherent account of how the trial was conducted. Since the tool was put in production, we have observed an increase in the number of reported issues and a decrease in the median issue resolution time which, along with the positive user feedback, point to marked improvements in quality, transparency, productivity, and teamwork.

Authorized Service Vendors in Mobile Terminals Voice

This study examines whether authorized service vendors (ASV) for mobile terminals (MT) are satisfied with the original equipment manufacturer (OEM) in terms of service provided to them and also how the ASV is performing at their premises. A seamless relationship between the OEM and the ASV is essential for both sides to prosper in this business. When the ASV supplies good services to end-users, this contributes to an increase in the customer satisfaction rating, loyalty and retention. The study employs an exploratory research design; in-depth survey interviews were carried out in six different ASV in Europe. The study was conducted at Nokia Corporation in Finland. The survey analysis of the association between category variables is descriptively analyzed. The main findings in this work were that the ASV is satisfied with the MT product manufacturer, and that the internal working practice of the ASV organization was perceived as more positive than negative. From the OEM side, the issue resolution time (iRT) and training before product launch are items that should be focused on in the first place, as these affect customer satisfaction. The ASV management should seek a way to share the end-user customer feedback to the ASV teams, and internal information communication should also be improved.

How commercial involvement affects open source projects: three case studies on issue reporting

Whereas most research on Internetware has focused on new technologies for keeping track of a changing Internet, little attention has been paid to the software development process. A large portion of the software running the Internet is open source software. Open source software is developed both by volunteers and commercial companies, often jointly. Companies get involved in open source projects for commercial reasons, and bring with them a commercial software development process. Thus, it is important to understand how commercial involvement affects the software development process of open source projects. This article presents case studies of three open source application servers that are being developed jointly by a volunteer community and one primary software company. We are interested in better understanding developer behavior, specifically task distribution and performance, based on whether the developer is an external contributor, e.g., a volunteer working in their spare time, or a commercial developer from inside the primary backing company who is being paid for their time. To achieve this, we look at issue reporting as an example of commercial involvement in open source projects. In particular, we investigate the distribution of tasks among volunteers and commercial developers by studying the source of reported issues and quantify the task performance on user experience via the issue resolution speed. We construct measures based on historical records in issue tracking repositories. Our results show that, with intensified commercial involvement, the majority of issue reporting tasks would be undertaken by commercial developers, and issue resolution time would be reduced, implying a better user experience. We hope our methods and results provide practical insights for designing an efficient hybrid development process in the Internetware environment.

English

  It may be intuitive to assume that the quality of issue corrective actions (iCA) for customers with mobile terminal (MT) issues can be improved by collecting samples of the faulty products in question for verifying the issues reported from the field. This study was created to test this hypothesis using three different established statistical analysis methods: binary logistic regression, Kruskal-Wallis statistical tests and Mood’s Median Test. The methods are used because the data collected from in-house database tool is categorical. In this study, these methods were employed to test if the presence or absence of corrective actions process (CAP) samples had any effect on the perceived quality of issue corrective actions (P-QoiCA) or any effect on the perceived quality of issue resolution time (P-QoiRT) for service to the customers. This study also examined the effect of the quality of the collected samples (QoSa) on the absolute issue resolution time (iRT). The study checked if the frequency of requests for samples differs between MT products of different software platforms (SW_P). Additionally the paper investigated how the sample collection turnaround time (SC-TAT) differed in different sales areas (SA). The main findings were that the collected samples had no measurable effect upon the P-QoiCA or on P-QoiRT.  Also it has been shown that QoSa and the SC-TAT had no effect on the absolute time (iRT) to resolve customers’ issues. In addition to the aforementioned findings, the study noted as an aside that the Moods’ median test found significant differences in iRT between different software platforms (SW_ P).   Key words: Corrective actions process (CAP)-samples, non-parametric tests, log-normal distribution, logistic regression, perceived quality.

Applying Self-Organizing Maps Method to Analyze the Corrective Action’s Quality Provided to Customers with Mobile Terminals

In the after market phase, responding to issues raised by customers within a reasonable time is crucial. Another factor which is important to customers is the quality of the issue corrective actions (QoiCA). This paper analyses the QoiCA from the user’s perspective, regarding the quality of corrective actions provided through an in-built tool (GENIUS) used within corporations. A survey questionnaire was sent to different participants in the network chain which handles or resolves the issues. The participants were from 17 European countries and 7 non-European countries. Responses were analysed, using statistical methods and the Self Organising Map (SOM) model and results were used to pinpoint or suggest the areas that are seen as opportunities for improving the quality of the corrective actions provided. Higher quality of corrective actions, along with other initiatives, will help to improve customer’s satisfaction. Three of the clear issues observed in this paper that contribute to long issue resolution time (iRT) are: 1) Long time to receive samples; 2) High frequency for asking more information from lower levels; and 3) Business impact price tag, to allow the issues to be prioritized, were missing from the escalated issues. QoiCA is jeopardized when: 1) A poor description of the issue is provided by the creator of the issue; 2) A poor response to the default requested additional questions (information) regarding the reported issue on top of the issue description. The authorized service vendors (ASV) users need more training with the in-built tool so that they know, for example, where to get help when they need it. When customer issues are resolved satisfactorily, there is a much higher chance that the customers involved will remain satisfied and loyal.