-
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
[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.
I very much like many features of Next-Gen projects, but without this feature their usability is severely reduced. I will not mark issues as "Done" that aren't done – this is a lie results in an inaccurate picture of both progress and the state of the product.
So I end up making constant backups of my project, every time I have to close an issue with any other status, which is a pretty ugly and unnecessary overhead.
Please implement this!
As a Product Manager, saying "no thanks" to some ideas is one of the best services I can give to my team and to my organization. We remove the distractions from our product backlogs, so that we can keep our teams focused on the most valuable things first.
Without the ability to close issues with resolution besides "done", I can't "say no" anymore and remove the distraction from our backlogs - at least not without misrepresenting an issue (or deleting it altogether).
This restriction would never fly for a Service Desk team closing out customer issues - software teams need this too!
Loving the simplicity and flexibility of the Next-Gen projects! The only downfall I have found so far is the lack of being able to specify a Resolution. This feature is such a necessity to so many. Please consider adding this to the Next-Gen projects.
I'm actually quite shocked this doesn't exist in the next-gen projects.
Typically when I find something isn't done to my style in Jira, I just adapt to the "Jira way" and move along. The lack of this feature, though, is incredibly baffling and I now have to migrate my hundreds of tickets to the classic Jira project because the lack of this feature alone makes the next-gen project unusable.
The resolution field is SO important, it distinguishes between tickets that we actually worked on ("Done") and those that were closed out for another reason ("Won't Do", "Duplicate", "Not a Bug"). Otherwise, I'd have to create a new "Status", but it will never be in a finished "green" state because I'm only allowed one of those.
This is honestly a catastrophe. Please do something about this!
If the Jira team decides to resolve this as WONTFIX, could they please tell us how they did that?
Not having a resolution field anymore is a setback compared to previous Jira setup. Without a resolution, we lack the granularity needed on how & why a ticket was closed.
Please prioritize it.
This should be #1 on the To-Do. That tickets don't have a reserved Closed status, that you have to either 1) record tickets as Done, which they're not, or 2) delete me (which is extremely bad practice, and unacceptable in regulated industries) is an absolute travesty.