-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Issue Summary
When a Jira instance has a default Resolution value, it can cause some issues to be marked as Resolved upon creation.
Steps to Reproduce
- You create a default resolution - https://<your-jira-instance>.atlassian.net/secure/admin/ViewResolutions.jspa
- Ensure your create and view screens match at least
- Create an issue, which auto-populates a resolution
- Issue by default is checked off since it has a resolution
Expected Results
If the issue has just been created and is not yet in a 'Done' status, then it should be unresolved.
Actual Results
In this configuration, a new issue will be marked as resolved with the issue key crossed out.
Workaround
Have no default resolution OR remove Resolution field from the Create screen.
There is no UI option to remove the 'default' from the resolution values, but this can be done by navigating here: https://<your-jira-instance>.atlassian.net/secure/admin/MakeDefaultResolution.jspa?atl_token=XYZ
Instructions on clearing values from the Resolution field may be found here:
- Using a workflow transition and bulk update: https://confluence.atlassian.com/jirakb/howto-bulk-clear-resolution-635896313.html
- Using automation: https://confluence.atlassian.com/jirakb/clear-resolution-field-in-tickets-with-automation-instead-of-workflow-post-functions-1236437759.html
- mentioned in
-
Page Loading...