-
Suggestion
-
Resolution: Duplicate
-
2
-
According to this comment, Jira has no plans to add the ability to have multiple resolutions for an issue.
This means, although we can mark an Issue as 'Done', there is no easy way to mark an issue as:
- Closed - As Duplicate of another Issue.
- Close - As "Won't Do".
Without this feature we are forced to either:
- Delete the issue, (losing all the valuable digital assets that are related to it)
- Mark this issue as Done (providing misinformation to the rest of team who may, naturally, come to the conclusion that all work in the issue is completed).
Please add a feature to allow multiple resolutions in Next Gen projects.
We cannot migrate to Next Gen until such a feature is added.
Update 27 Aug 2020 — blim2@atlassian.com :
We don't expect to have resolution in Next-gen this year. However, we are targeting to support multiple "Done" statuses in Next-gen by the end of the year.
- duplicates
-
- Under Consideration
- is duplicated by
-
JSWCLOUD-20518 Canceled or Won't Do option for next-gen projects
-
- Closed
-
- is related to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWCLOUD-18435] Multiple resolutions - Resolve a Next Gen issue as something other than 'Done'
Thanks df02d245fa47 for pointing out that extremely silly mistake by me - the shame of doing it on this suggestion! I've updated the resolution to Duplicate.
All - can all of you voting and watching - please do so again on https://jira.atlassian.com/browse/JSWCLOUD-17499
Apologies for the inconvenience but we have noticed these suggestions are duplicates of each other.
We are currently working on allowing multiple Done statuses per column which will hopefully provide some relief in this area, and customising resolutions is something we are considering for the longer in next-gen projects.
Thanks
Eoin
This appears to be in-work over here: https://jira.atlassian.com/browse/JSWCLOUD-17434
john1055459598 No worries. Sorry for the delayed response on this ticket. Let me update the description. Please don't hesitate to reach out with more questions/concerns.
I would update my Issue description above, to make a correction, but I cannot seem to edit it at the moment.
Thank you for clearing this up, Blim, that's great news. Your strategy makes sense and I totally understand. I am glad you recognise the issue.
Hey ya'll – totally understand the frustration here. My name is Bryan and I'm a Product Manager working on Next-gen. We're placing higher priority on things like introducing workflows to Next-gen <https://jira.atlassian.com/browse/JSWCLOUD-17434> and overall performance (e.g., https://jira.atlassian.com/browse/JSWCLOUD-18724) before we introduce resolution.
I wouldn't say that we "have no intention of implementing this feature", but I can say with rather high confidence that resolution won't be coming to Next-gen by the end of the year. FWIW, we're hoping to introduce the ability to add multiple "Done" statuses to Next-gen by the end of the year. We will then revisit resolution after.
Thanks for your feedback and feel free to keep leaving comments and questions on this ticket.
Yes. I am coming to think that the reason why Atlasssian have no intention of implementing this feature is because it is impossible given the design's architecture.
Perhaps renaming the word for the status from "Done" to "Resolved" could at least get some way to making the status more honest.