John Funk Community Champion

And a little more for your reading :-) https://community.atlassian.com/t5/Next-gen-questions/Remove-issues-from-next-gen-Kanban-board/qaq-p/1210409

Hi Jennifer - you might refer to this other post for guidance: https://community.atlassian.com/t5/Jira-Software-questions/How-do-you-manage-releases-on-next-gen-boards/qaq-p/914518 There short of is that there is no way to do releases right now on Next-gen boards. 

@yogananda - If this answered your question for you, can you click on the Accept Answer button above to close this one out? Thanks!

Hi @Matias Silversteyn - did any of these answer your question for you? Is there anything else we can help guide you with? If not, can you click on the Accept answer button for those that provided the answer for you so we can close this one out? Thanks!

Hi @Yuliia Zhyliaieva - You can use Epics with a Next-gen project if you like to get the Roadmap feature. But at that point, I would close out the Epic and create new issues in the Classic project. As Jack said with his excellent comments, I would not do a Move from one to the next to continue the same work. 

Hi Edie - I am just a user like you. I can pass along your comments, by you should do that directly with Atlassian. 

Great! Glad we could help.

Hi @Bearcat M. Şándor - Sorry for the poor wording. You are correct, you do not copy the project, you create a new one and use the Create with Shared Configuration option. Then you select the "template" that you previously created. I hope that is clearer!

If that works for you, can you click on the Accept answer button above so we can close this out? If it doesn't let me know if there is something I can help with. :-)

I am using the Jira Cloud for Excel (Early Access) free plug-in. I was able to relatively quickly open a filter in Excel and download all of the issues (or just put in a JQL query on the spot. Not ideal, but it worked. 

Hi @yogananda - You might want to refer to this similar post. It doesn't look like it will be changing back in the short term.…

@Lorraine Gorman - Thanks for the update. 

I think you hit it on the head with your comment: "How my company handles accountability is not Atlassian's problem to solve." And just for clarification - this is not Atlassian's comment that it is their most asked question. This is just the observation of a single user. 

Hi Julien - Welcome to the Atlassian Community! I am pretty sure you can do this with the add-on Automation For Jira. Take a look at this link to see if it provides the information you need.…

Hi Barbbora - Welcome to the Atlassian Community! What are you using now to mark the Epic done when at least the story is done? Are you using an add-on for that? If so, which one? 

Glad you are able to better use it now. :-)

Hi @Violetta Balayan - You have to delete one of the fields if there are already 3 before you can add a new one. If that still doesn't work for you, you might want to try to copy the board, and see if the new board will let you do what you need. Then just delete the old board. 

Understood :-) Best way is often to give one or other a try and see which one works best. I tend to use a lot of groups and then attach permissions to the groups using the People functionality under project settings. 

You should add a new Status to your workflow for Discard (and maybe Aborted). See this blog for more information on how those can (should?) be used. :-) https://blog.huge.io/kanbans-four-conclusions-5cfb1716fa39 Full disclosure, it was written by my boss. :-)

@Swapna Reddy - Welcome to the Atlassian Community! It is best to copy the Simplified workflow, then make the changes in the new workflow while it is is still Inactive. Then you will need to create a new Workflow Scheme for the new workflow and attach them. Finally, go into the project > settings, click on Workflow Scheme…

Hi Darren - you might be better off just Discarding or Aborting the issue. It's a pretty good policy to delete very few things if any, even for duplicates or mistakes. 

Hi @Speak Jira administrator - check the Permission Scheme to see if you have the Manage Sprints permission. 

I will weigh in that I think it's a really bad idea to have two people assigned to an issue. We treat the assignee as the owner of the issue and they are responsible until someone pulls the card from them and takes ownership. That's more of a Kanban best practice than anything. If you find you have multiple people working…

Try adding a new column to the board and see if that helps you. 

Hi Will - Welcome to the Atlassian Community! Is this a Classic Project or a Next-gen project? 

Hi Anil, You might be able to do something like that with Automation For Jira. You could have a rule that checks for when the field is updated and if the Uncheck-All option is selected, then clear the field. This would not happen real time but when the user saved the value for the field. In other words, as soon as they…

@Dionei Piazza - Did this answer your question for you? If so, can you click on the Accept answer button above to close it out?

Hi @Dionei Piazza - Welcome to the Atlassian Community! One way to solve that is with a single project and workflow like you have it. Then create a Group for each Squad and place the members in it. Then put Conditions on the Transitions to the phase that allows only that Group (Squad) to access it. Another way to do it…

Hi Lorraine - I am experiencing the same thing. Trying to get some feedback, but none received yet. 

Ah, I don't think Next-gen projects are available on Server. https://community.atlassian.com/t5/Next-gen-questions/Are-Next-Gen-projects-available-in-Jira-Server-version-or-only/qaq-p/950218