Qt wiki will be updated on October 12th 2023 starting at 11:30 AM (EEST) and the maintenance will last around 2-3 hours. During the maintenance the site will be unavailable.
Jira Tips and Tricks: Difference between revisions
AlexBlasche (talk | contribs) |
AlexBlasche (talk | contribs) |
||
| Line 19: | Line 19: | ||
| NMI & RNMI label set || NMI and RNMI will be unset if the reporter posts a comment. || After 2 wks of no activity, the issue is automatically closed with an appropriate message. | | NMI & RNMI label set || NMI and RNMI will be unset if the reporter posts a comment. || After 2 wks of no activity, the issue is automatically closed with an appropriate message. | ||
|- | |- | ||
| <<No NMI label>> || Any comment from the assignee renews the NMI label. || Issue will be transitioned back to "Reported" state (after | | <<No NMI label>> || Any comment from the assignee renews the NMI label. || Issue will be transitioned back to "Reported" state (after 1 day without activity). The assumption is that further information was provided but the user forgot to transition the issue. | ||
|} | |} | ||
Revision as of 14:03, 19 November 2018
Jira Automation
This page describes automated processes which might be useful to understand when working with Qt's bug tracker Jira https://bugreports.qt.io
Need More Info (NMI) handling
Qt's bug tracker utilizes the "Need more info" (NMI) state which indicates that the current assignee of a issue or bug requires more information from the reporter. The issue remains in the state until the reporter has provided the requested information. The information can either be provided by commenting or updating the issue description. Once the info was provided, the reporter must transition the issue out of the NMI state by pressing the "Provide Missing Info" button. The overall purpose of this state is to ensure bug reports with as much information as possible and being able to identify incomplete ones.
Unfortunately not every reporter (especially reporter new to the Qt community one) is aware of the obligation. Therefore an automated cleanup procedure is employed to remind reporters of their obligation and (if necessary) prevent issues from being stuck in the "Need More Info" state. After two weeks of inactivity a reminder is posted to the Jira issue stating the expectations from the reporter and another two weeks of inactivity automatically close the issue (with an automated explanation).
The following table provides a summary of the automated handling in Jira. Workflow conditions are recorded via Jira labels. At the same time manual control of the cleanup procedure by the experienced users is permitted. The table assumes that the issue at hand is in the NMI state.
| Set issue label | Expectation | Automated handling |
|---|---|---|
| NMI label set | The reporter must provide additional information and should transition the issue out of NMI. Any comment from the assignee will unset the NMI label | After 2 wks of no activity, the RNMI label is set. Setting of the RNMI label will trigger the posting of a comment to the reporter. |
| NMI & RNMI label set | NMI and RNMI will be unset if the reporter posts a comment. | After 2 wks of no activity, the issue is automatically closed with an appropriate message. |
| <<No NMI label>> | Any comment from the assignee renews the NMI label. | Issue will be transitioned back to "Reported" state (after 1 day without activity). The assumption is that further information was provided but the user forgot to transition the issue. |