Issue Tracking Sample Clauses

Issue Tracking. 6 The JIRA issue tracking application will be used to report all data quality issues to 7 the appropriate personnel for research and correction activities.

Issue Tracking. The sector manager will report all data quality issues to the 16 appropriate NOAA personnel for corrections through the JIRA issue tracking application 17 implemented by NOAA.

Issue Tracking. Customers enter their issue into the tracking service where they can monitor its progress. During the resolution process, the customer and support engineers can add comments, upload attachments, and update the status. • Web / Email / Phone Support - Depending on the level of support, customers have access to support engineers through the web, email, or phone.

Issue Tracking. The Company utilizes an issue tracking system, called mTrack. This enables all parties to view the status of any issue at any time to determine the progress of issue resolution. All issues sent to our support services team via email are automatically uploaded into the mTrack system. Any issues called in via phone, or text, will be entered into mTrack by the Company’s support services team. The URL for the tracking system will be sent to the Client team once the contract has been executed.

Issue Tracking. Licensor reserves the right, at its own discretion, to implement an issue tracking system1 to facilitate support and maintenance services, as the case may be.

Issue Tracking. Contractor shall implement an effective system for recording and tracking requests for clarification and instructions, submittals, approvals, information and other responses from the Architect, Agreed Changes, Change Directives, Change Requests and other communications that define or raise questions about the Work. At each weekly progress meeting, Contractor shall identify and raise for discussion any open issues that may impact the schedule or cost of the Project.

Issue Tracking. ‌ Tasks tracking is crucial for measuring the actual progress of every project. For MICO, based on our previous experience, we have chosen Jira28 for such need. Jira is a proprietary issue tracking product, developed by Atlassian; it provides bug tracking, issue tracking, and project management functions. In addition to the regular Jira, two plugins have been enabled too: Jira Agile29 for supporting agile development, and Jira Capture30 for helping us to build and fix the user interfaces of the prototypes produced by the project.

Issue Tracking. GitHub Issue tracker)

Issue Tracking. Upon identification of project issues, risks, and key project decisions both Tyler and City team members are responsible for adding the issue to the Issue Log. For each identified issue, the following information will be captured: ▪ Issue Number ▪ Reported by/date ▪ Status (i.e. new, open, closed, pending) ▪ Module/Business Process ▪ Priority ▪ Issue ▪ Comments ▪ Findings ▪ Recommendations ▪ Resolution Assignment ▪ Date Tested ▪ Date Closed The City and Tyler project managers will review the Issues Log on a bi-weekly basis during project team meetings, more frequently if needed. The City and Tyler project Managers will collaboratively assign a priority to each issue and identify the individual(s) responsible for facilitating its resolution. During the critical phases of the project, the City and Tyler project managers will review the issues log on a daily basis. Issues identified through the Issues Log will be resolved by the implementation team or the Tyler implementation team will coordinate as necessary with Tyler’s internal resources. The City will not be responsible for making direct contact with Tyler support for issues identified on the issues log unless a critical issue is encountered while Tyler implementation staff is not onsite and the issue prevents City staff from making appropriate progress.

Issue Tracking. Customers and other users might report issues if unexpected events or behavior occurs in the system. Issue tracking is concerned with managing these issues, associating them with efforts to resolve any underlying problems in the system, and informing customers of possible resolutions. Operators often perform issue tracking by using a separate system that enables them to record and report the details of problems that users report. These details can include the tasks that the user was trying to perform, symptoms of the problem, the sequence of events, and any error or warning messages that were issued. The initial data source for issue-tracking data is the user who reported the issue in the first place. The user might be able to provide additional data such as: • A crash dump (if the application includes a component that runs on the user's desktop). • A screen snapshot. • The date and time when the error occurred, together with any other environmental information such as the user's location. This information can be used to help the debugging effort and help construct a backlog for future releases of the software. Revised: January 11, 2021 Different users might report the same problem. The issue-tracking system should associate common reports. The progress of the debugging effort should be recorded against each issue report. When the problem is resolved, the customer can be informed of the solution. If a user reports an issue that has a known solution in the issue-tracking system, the operator should be able to inform the user of the solution immediately.