Configure workflow - Nextgen project

[Ankur Parashar]

How do I configure the issue workflows for a nextgen project type?

[Elliot Gates]

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. 

[Vinayakaram Nagarajan]

Absolutely agree

[Sergei Gridnevskii]

I cannot add a Failed or Cancelled or Rejected status to an issue. So what's the point for Jira then?

[Ann S]

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.

[Daniel Eads]

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

[Edward Strickland]

Work flow seems to be missing from the latest version of the upcoming features has this been dropped?

[Paweł Iwaszko]

Removing custom workflows from the roadmap would be unfortunate. 

[Edward Strickland]

indeed 

Can someone clarify?

[Simon Williams]

This would be a huge loss for Jira and would make me search for an alternative

[Daniel Eads]

Hey all,

Some clarifications:

• As of the writing of this post, workflows are not explicitly listed on the coming-soon features page. They are however on the development roadmap for the Next-Gen team. Keep an eye on the coming-soon page for an idea of when it is about to ship.
• Classic projects are still available with custom workflows. If you need a customized workflow, Classic projects are where you want to be for now.

Next-Gen is still under active development and shaping up. Our development teams are interested in hearing your feedback - the bottom of the sidebar in next-gen projects provides a quick way to send feedback right from Jira:

Fill out the form and hit Submit! I would suggest using Features as the option about custom workflows.

Cheers,
Daniel

[Angelo Georgetti]

Daniel, the workflow that we see when we attempt a bulk operation is out of sync with our current board settings.  We created a project with names we quickly abandoned once we figured out how the Next-Gen project worked; however, when we go to perform a bulk operation the initially rejected names are the names on the columns, not the current names.  Are original names attached to columns hardcoded into the system? If not, what fix do you suggest? 

We were on an extensive call with a JIRA product manager yesterday and virtually every feature we sought clarity on/asked help with either could not occur within the Next-Gen framework or had yet to be developed, which was really discouraging from a UX standpoint.

[Alexandru Bujor]

Honestly I am tired with Atlassian creating new stuff that misses relevant functionality present in previous versions of the same stuff.

[Andrea Stemp]

Workflow customization is a necessity!

[Vinayakaram Nagarajan]

Just absurd you dont have workflow customization! I cannot merely add a 'cancelled' to workflow!

[Dmitry Melikov]

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

[a a]

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. (

[Graham]

@Dmitry Melikov Is there any timeline ETA on this? Page just says 2020.

[Jobi Varghese]

@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

[M Shofwan Amrullah]

still no updates?

[aliasgarmurtaza]

Any updates? It still shows 'releasing in 2020'. 

[Ollie Guan]

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

[FS]

See feature request https://jira.atlassian.com/browse/JSWCLOUD-17434 and add your vote...please :)

[Beth]

I might have begged, a little. No shame.

[Mat Chavez]

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...

[Edward Strickland]

Which Atlassian has bought ;) 

[Beth]

Wow, they did? I hadn't heard that! We really need workflows to be able to use this.

[Stephen Paschall]

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.

[Rick Siedle]

Such a shame. I just can't move without workflow either. A lot of the other simplification is awesome. You accidentally took the kitchen sink out too. 

[Deleted user]

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:

[Justin Gross]

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.

[M Shofwan Amrullah]

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. 

[Mike Pearson]

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

[Rob Vice]

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?