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. 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 - An issue is a single support incident with a JumpMind product and the reasonable effort needed to resolve it. A single support issue is a problem that cannot be broken down into subordinate parts. Named Contacts - Support is provided to the Named Contact(s) provided by the Customer. End users requesting assistance will be redirected to their respective Named Contact. Service Level Agreement Support Access - Customers gain access to support engineers during business hours (9 am to 5 pm Eastern Time, except holidays).
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. GitHub Issue tracker) Another critical aspect of SUBSOL development lifecycle is issue tracking. Regardless of how carefully and detailed the software was tested before going online, there always will remain bugs and problems that haven’t been fixed yet. Therefore, it is necessary to install right from the start of the development process an issue and bug tracking system. An issue tracker accessible to every developing partner of the SUBSOL project has been installed to manage development issues such as problem reports, feature requests, and work assignments. For issues concerning coding, features and distribution the GitHub issue tracker has been chosen.
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. Requirements for issue tracking 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. Data sources, instrumentation, and data-collection requirements 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 Analyzing issue-tracking data 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.
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. 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. If and to the extent relevant, section 9 of the General Terms and Condition shall apply.
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.
