Our team are long time Trello users, and this past week we decided to try using Jira due to some of the benefits it would bring us.
We're using a next-gen project, and so far have everything working how we'd want/expect. We have enabled roadmap, backlog, estimation, and pages.
One thing we just can't seem to work out is how to (in the Trello venacular) "archive" an issue, i.e. "resolve" or simply "close" an issue.
I feel like I'm being really stupid here as I just can't find what I assume is a very simple option. When I click the menu button on an issue I can see the option to delete, but I can't see any options to resolve or close. When I select delete, the dialogue box asks,
You're about to permanently delete this issue, its comments and attachments, and all of its data. If you're not sure, you can resolve or close this issue instead.
Can you even resolve or close issues in a next-gen project? Is there a setting somewhere else to enable this functionality?
I don't think this is possible. As you can see in the following links some people have the same question:
Hope this helps!
can you tell me where exactly that is possible? The new Issue View is activated but where exactly can I change the resolution? The Status I can change but the case is what if something is not Done but won't be done as it is not reproducible or won't be fixed? Thanks for clarifying
I managed to figure out a workaround with the Automation for Jira app. It works with next-gen projects, so I just set up a simple trigger to set the resolution to "Won't Do" and it worked perfectly! :)
I'm using the free version of the app: https://marketplace.atlassian.com/apps/1215670/automation-for-jira-cloud-lite
@Adam_Sigel Sure. This is for a project our support team uses to track feature requests. We have an issue status for "Won't Do" that needed a "Won't Do" resolution. The automation is simple:
I have to chime in here. It is ridiculous to think that everything can just be marked as DONE. There are different types of DONE (as others have mentioned). Such as "could not replicate", "will not fix" - to name the ones I can think of. "DONE" is a specific state which is a variation of "CLOSED" - as are the others mentioned.
This really needs to be a feature as I have inherited a backlog that needs this type of treatment and I have been polluting sprints with these to ensure they are at least being tracked in some way.
I like next-gen better than the previous templates but this definitely needs to be fixed.
I wonder if anyone could help - I am in the process of setting a project up using the Kanban Next Gen board. I understand that "done" tasks will automatically be removed from the board after two weeks if untouched. Please could you let me know if they will also be removed from the board section of the backlog list after two weeks as well? I'm concerned that I will be left with a long list of "done" items on here too.
I seriously wonder why nobody of Atlassian did react so far. This is what I did (New Gen Agile) - adding a "Dropdown" field to the ticket type calling it "Resolution" with the according options like "done", "won't do", "duplicate", etc
its in Project Settings > Issue Types
Does anyone know when/if this is going to be fixed so that issues can be closed? We can have 20-30 "done" tickets sitting around at any one time and it makes it difficult to see the wood for the trees when managing backlog etc. Waiting 14 days is not a great "solution" and I don't see why there can't be a way to close off manually.
The accepted answer on this thread isn't remotely helpful.
Another workaround we're using
To get around the issue of not being able to 'Close' a ticket as 'Won't do', 'Resolved', 'Duplicate' or other status we've just moved tickets to Done, add an appropriate label such as 'Won't do' and added the reason that explains why as a comment.
Why closing a ticket is important and should be considered on the Roadmap for 2020.
There's plenty of valid reasons as to why you should be able to Close a ticket and makes no sense you can't. You make plans, and then sometimes plans change, perhaps radically and justifiably, but makes no sense to delete all knowledge of their previous plans existence. Good housekeeping of the backlog means keeping it free of things that are not an immediate priority and that you cannot commit to a realistic timeline of when you might come back to it so closing until such time you want to come back to it is really helpful.
What is the Atlassian recommended way of handling this in NextGen?
There are plenty of cases where a ticket is closed as "Won't Do" or "Works for Me" and then later on the ticket becomes important because it contains context and relevant data when the underlaying problem gets identified. Deleting the "Closed, Unresolved" ticket rather than keeping in the system for context and background is not a viable approach.
I will look at the "Conclusion" field to see if this can work for my team.
I had no luck in finding the "Conclusion" field in my NextGen or Traditional projects.
Closing a ticket to an unresolved state is key to JIra functionality. As a work-around my company has defined an Epic "won't do" and we allocate tickets to this epic. It is a nasty hack that at least allows us to write some filters to hide these tickets.
Ultimately, this breaks most of the Jira functionality around sprint reports and sprint planning. But it seems like Atlassian is no longer interested in making products that serve the needs of the customer.
Is it really the case that Atlassian is marking the feature request for a "won't do" conclusion as "won't do"? If so, how is this being reflected in the Jira project for Jira?
(It's meta- all the way down.)
Hi Atlassian Community! My name is Ivan, and I’m a Product Manager on Jira Software Cloud. Project admins are spending hours a week tracking their team’s work on their boards. End users use the b...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events