Jira Tips and Tricks: Difference between revisions

From Qt Wiki
Jump to navigation Jump to search
(First draft)
 
No edit summary
Line 3: Line 3:
This page describes automated processes which might be useful to understand when working with Qt's bug tracker Jira https://bugreports.qt.io
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 handling ===
=== Need More Info (NMI) handling ===


Qt's bug tracker utilizes the "Need more info" 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 "Need More Info" state by pressing the "Provide Missing Info" button. The overall purpose of this process is to have issues and bug reports with as much information as possible and being able to identify incomplete ones.
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 this 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.
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.
 
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.
 
{| class="wikitable"
|-
! 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 reset the NMI label || After 2 wks no activity, RNMI label is set. Setting of the RNMI label will trigger the posting of a reminder to the reporter.
|-
| NMI & RNMI label set || NMI and RNMI will be reset if the reporter posts a comment. || After 2 wks no activity the issue is automatically closed with an appropriate message.
|-
| <<No label>> ||  || NMI and RNMI label are not set. Issue will be transitioned back to "Reported" state (after 2 wks without activity). The assumption is further information was provided but the user forgot to transition the issue.
|}

Revision as of 13:36, 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.

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 reset the NMI label After 2 wks no activity, RNMI label is set. Setting of the RNMI label will trigger the posting of a reminder to the reporter.
NMI & RNMI label set NMI and RNMI will be reset if the reporter posts a comment. After 2 wks no activity the issue is automatically closed with an appropriate message.
<<No label>> NMI and RNMI label are not set. Issue will be transitioned back to "Reported" state (after 2 wks without activity). The assumption is further information was provided but the user forgot to transition the issue.