How do I configure the issue workflows for a nextgen project type?
Hi @Ankur Parashar,
I think the next-gen project is different from other Jira project types.
You can do simple process configuration by adding columns and setting rules.
https://confluence.atlassian.com/jirasoftwarecloud/working-with-next-gen-software-projects-945104895.html
Hey Ankur,
Unfortunately workflow customization isn't available yet for Next-Gen projects. It is on the longer term roadmap though! You can take a look at the recently shipped and coming-soon features of Next-Gen projects here. The note about workflows is on a Community post by one of our product managers discussing features.
Cheers,Daniel
Work flow seems to be missing from the latest version of the upcoming features has this been dropped?
Removing custom workflows from the roadmap would be unfortunate.
indeed
Can someone clarify?
The lack of feature parity is why we haven't moved, and won't move to next-gen. There are PLENTY of services that do 1:1 without custom workflows. That's JIRA's *advantage*! Without workflows, what's the point? I can get plenty of free options or much cheaper options... it's the custom workflow that makes it (barely) worth the money.
If Atlassian removes this, may as well just use Trello...
Which Atlassian has bought
Wow, they did? I hadn't heard that! We really need workflows to be able to use this.
We're right there with you. This is an absolute must-have feature for any sizable team. I'd love to have the luxury of time to spend breaking stories up discretely enough that the default workflow was sufficient, but we'd spend so much time managing dependencies and shuffling task meta that we wouldn't actually accomplish the tasks themselves.
As it is, a next-gen project is little more than a task list. There are many less expensive (and more intuitive) solutions in that space.
See feature request https://jira.atlassian.com/browse/JSWCLOUD-17434 and add your vote...please
I might have begged, a little. No shame.
I understand next-gen is intended to be easy-to-use and quick to set up but they've absolutely stripped this back to the bare-bones. One board, per project, and now you cannot even customise the flow?
The roadmap feature is incredibly useful, if this was implemented in 'Classic Projects' there would be no need to move.
Absolutely agree
I cannot add a Failed or Cancelled or Rejected status to an issue. So what's the point for Jira then?
Having an additional step in the workflow is much better than just To Do and Done.
Particularly, because we stage work or use a review step. Do we need to task out those steps as well in order to get this basic functionality of the original JIRA workflows vs. nextGen?
Hey all,
I am happy to announce that a new workflow editor for Next-gen projects is at the last stage of development and will be shipped very soon.
You can find more details on our Next-gen "what's new" page (see "Reimagining the workflow editor" section): https://www.atlassian.com/software/jira/whats-new/next-gen
I am happy to answer your questions!
Cheers,
Dmitry
Senior Product Manager, Jira Platform
Hi, It's very sad the most need functional was removed from new type project and it's not availble now. It's really wonder, how could be that? It's not increasing functionality but excluding options and tools without any good replacements . So, there is a problem if worklfow-service "will be back" only in 2020. (
@Dmitry Melikov Is there any timeline ETA on this? Page just says 2020.
For anyone finding this as I did in my search, this may help you. I have a next-gen software project using the kanban template. I think next-gen is trying to force you into the sprint mind set which is why it seems you can't edit the workflow but you can. Anything that is not in the current sprint by definition cannot be 'in progress', etc. and is considered to be in the 'back log' and stuck in 'todo'. When you move it into the current sprint you can add stages, move them around and the kanban columns appear in the dropdown when editing the issue.
After I added "TESTING" to the kanban board it appears in the edit issue screen:
Additionally, if you have an "aggregate" board that contains issues from multiple projects (can be both next-gen and classic), you will need to "map" that status to one of the columns under "columns" settings for the "aggregate" board. Then you can manage issues from multiple boards under a single "aggregate" "master" planning board.
@Dmitry Melikov I want to start using Next-Gen projects. Just wanted to check with you on the release dates of the workflow editor. Any timelines on this. Please let us know.
Thanks
But you still can't have more than 1 end-state. For example, I want to have both DONE and CANCELLED as my end-state (that green-colored status). Now all of my CANCELLED tasks are still considered not done or "in progress" by Jira. That's very frustrating.
Next-gen wasn't ready for rollout without the user being able to edit the workflow which also means issue types cannot be edited (e.g., can't add blocked status to an issue type). This feature has been in progress for two years: JSWCLOUD-17434.
This seems to be available now.
For Next-Gen projects, go to Project Settings > Issue Types > Story
At the top of the page, next to the "Story" title, is an "Edit Workflow" button
It looks like you're new here. Sign in or register to get started.
