-
Notifications
You must be signed in to change notification settings - Fork 192
How to resolve JIRA issues
Melanie Clarke edited this page Mar 31, 2025
·
10 revisions
If the Pull Request has an JIRA issue associated with it (most should have), after it is merged:
- Open the ticket in JIRA
- Click on the last tab on the top, which identifies the state of the ticket and choose Resolve Issue -> READY FOR TESTING.
- In the pop-up window that appears, set the "Fix Version" number to the DMS build in which this will be released and add a comment mentioning or linking to the PR number that fixed the issue. This will move the state of the Jira ticket to "Ready for Testing".
- If the issue was created by INS or needs testing by INS leave it at that.
- If the issue was created by a team member and has already passed internal testing, move the ticket to Closed. (Close Issue -> CLOSED)
When in doubt, ask Product Owner or Scrum Lead.
Troubleshooting note:
Sometimes, if a Jira ticket has an associated GitHub issue, when the GitHub issue is directly closed, the Jira ticket is set to "Ready for Testing" without setting an appropriate resolution status. The resolution status cannot be directly set in this state, so in this case, the Jira ticket needs to be reopened, then resolved properly as above. The Product Owner or Scrum Lead will clean this up, as needed.