nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

workflow for next-gen project

Alicia Y

Is the workflow setting just for classical agile project? I want to add workflow or import workflow from market into my projects, how come there's no such "publish workflow" in my jira setting? And how can I make inactive workflow active? Why cannot I assign the workflow to my projects? Is it because I am using the trial version? Need experts help as soon as possible, thank you.

Accepted answers

blim

Hello all,

Thanks for commenting on this thread and expressing your interest for workflows in next-gen. Today, workflow transitions are in production: https://community.atlassian.com/t5/Next-gen-articles/Feature-Announcement-Jira-Software-Next-gen-Workflows/ba-p/1545178

We hope to deliver different workflows per issue type in the next couple of months.

We will be shipping multiple Done's statuses and the ability to map multiple statuses per column by the end of this month (Feb 2021).

We will follow up with:
1. Different workflow for epics
2. Ability to unmap statuses from the board
3. Different workflows per issue type

Feel free to follow this ticket https://jira.atlassian.com/browse/JSWCLOUD-17434 for updates.

Best,
Bryan Lim
Product Manager

All comments

Daniel Eads

Hi Alicia,

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.

Workflows are made active by assigning them in a workflow scheme. In the screenshot, you're looking at all the workflows but the assignments are done in project settings. We've got documentation for this here, but in short the steps are:

Choose the Jira icon (, , , or ) > Projects.
Select the project you want to associate your workflow scheme to.
Go to your project and click Project settings.
Click Workflows. You'll see which workflow scheme the project currently uses.
Click Switch Scheme and select the relevant workflow scheme from the Scheme list.
Click Associate to begin the migration process. Each issue needs to have a valid status, so you may need to assign statuses to a select number of issues after you switch workflow schemes.

And for clarity, just stating again that workflows will only be able to be assigned for Classic projects currently. Keep an eye on that roadmap for when it will be available in Next-Gen.

Cheers,
Daniel

Elizabeth_hjjgnu

Hey Daniel - is there an update for when workflow customization will be available for next-gen projects?

Could you link me to an article that describes how to revert a next-gen project to the "old" project type?

Daniel Eads

Hey @Elizabeth !

We've got an article describing how to convert between Classic and Next Gen projects (both directions) available here. The basic idea is that you create a project of the type you want to be using, then move all the issues to your new project.

As for updates on feature availability, all the information we have available to share is on the public roadmap. This page shows all the features that have shipped to next-gen projects already as well as what's coming up the soonest. You can get a good idea of release cadence by looking at the dates on the already-released features. While workflow customization is not explicitly listed at the moment of this post, our product teams definitely are working on it and will add it to the roadmap when it is nearing release.

Cheers,
Daniel

Thomas Belknap

I see nothing in the roadmap that says anything about associating workflow schemes to next gen projects. Can we assume this will not be in the next gen projects, at all?

jillian_argbbw

Hi all,

I'm a PM at Atlassian, and I'm excited to tell you that we're currently working on adding a new Edit Workflow feature to next-gen projects!

We still have a bit of work to do, but you can watch this ticket to get updates on our progress.

Please don't hesitate to reach out to me directly at jstein@atlassian.com with anything you're hoping to see in next-gen workflows.

Cheers,

Jillian

Angie Ursic

Hey @jillian,

These are great news, would you be able to give us an update on the feature?

Also, is there a way to configure workflow triggers in next-gen project in the meantime?

Thanks in advance for your answer!

Best,

Angela

Jay_izxrm9

Really excited to see this but I see nothing in the nexgen roadmap

Matt Leavitt

@jillianThis is pretty core to your system, the ability to edit workflows. Can you explain why it the issue was entered as a ticket on 11/20/2018, but 11 months later, it still isn't even on your Jira Roadmap? What is taking you so long? We absolutely require this feature before updating to the next-gen, and we very much would like to do so to gain access to the Roadmap features. But you are holding us back by not prioritizing this essential feature (to many users).

UPDATE: The above-referenced ticket, JSWCLOUD-17434, was reassigned from Jillian Stein to Dmitry Melikov [ dmelikov@atlassian.com ] on 9/11/2019. So the issue is clearly not forgotten, but it would be good to see some progress on this after almost a year of nothing for such a core, critical feature.

UPDATE (10/22/2019): Well, they have finally updated the Jira Roadmap to add the custom Workflow editor! Just be aware that it is scheduled out for 2020 with numerous projects ahead of it. And knowing how software development can go...well, I wouldn't count on the beginning of 2020 - maybe a year from now is more realistic? I'm hopeful, but not holding my breath.

Tom Harkness

Hi,

Are there any updates for this at all? This is absolutely shocking that such a core component / function of the product is not available in what is meant to be the "next-gen" way of doing things.

Florian Kasper_vlr5tw

The next-gen projects are pretty useless if we don't have the ability to 1. reassign the type (it's all software project) and 2. it's impossible to change the workflow. Your workflow is heavy complicated - I guess that's the reason why Atlassian itself doesn't use their cloud-hosted version with a new-gen project. The standard workflow would be perfect for a business project! A software project should always contain the status QA-testing / review and blocked. @jillian please either enable this feature within a specific deadline or give us a tool to downgrade all new-gen projects to first-gen projects. Nobody got time to create first-gen boards again and move all stories over there.

Ben_Chamberlain

Adding that the workflow editor is really important. Just switched my project over to New Jira, and may have held off if I'd realized I couldn't edit my workflows. We have a way around it, but it's awkward, and doesn't do much for boosting the teams confidence in the change. Please don't de-prioritize this!

Nuwan Kanakarathna_lh5wbq

Still waiting to see workflow edit functionality on NG projects

Andrew Beak

This next-gen stuff is nowhere near being ready.

It's not as feature complete as much cheaper options offered by other companies.

It's the same with Confluence right now.

The question of missing features in Jira is actually best answered by saying "use something cheaper, that is ready for market".

Howard Davidson

Oh come on!

Martin Schenk_kalm1q

I remember when there was a workflow editor for next gen announced. Does anybody know, when it will be available? i promote digital workflows in my portfolio and cant wait to offer next gen to my clients.

Mark Ward_a3tsv1

giphy.gif?cid=790b761109d5df52ee9e6fc0421fdf527bf71248835df412&rid=giphy

senthilkumar6.n

Too bad that we don't have customized workflow in next gen. Because of this reason we are moving back to classic

Christian Ernst

Same with me. Created a next-gen project, issued some tasks, detected that the provided workflow is insufficient for software development, tried to assign an existing (modified) workflow/workflow scheme, found absolute no way of doing such, searched the internet, finally came across this entry.

Conclusion (at least for me):

Delete the "next-gen" project,
get rid of all "new Jira experiences", and
get back to good old classic Jira.

Robby Ibrahim_t6iu18

Hello from 2020.

Service Desk next-gen projects have Workflow and Automation settings but not Software next-gen projects. Odd. Real odd. Now, we have to add and pay for Agent licenses when we really didn't want to.

Ashwin Kumar H M

We cannot use Classic because we need Roadmap in Next-Gen. But Next-Gen is not letting me edit the Workflow. Next-gen seem to be waste of time.

Can one of you please tell me if there is better way in which I can include a Duration field using which Due Date should get calculated. https://www.youtube.com/watch?v=YQkLeGxoa0A&feature=youtu.be&t=319%C2%A0 suggests editing workflow. Is there any other way?

Mike_Illobre

Is there any news on when the workflows for next gen projects will be implemented. Also is there a way to convert a next gen back to the classic projects?

Amit Gaikwad_92iuch

@Mike_Illobre : I don't think so there this feature will be released soon. Also there is no way to convert the next gen project back to classic one.

But, there is workaround-

1. Create a classic project and set up a workflow in that project.
2. Now, migrate all the tickets of the next-gen project to that classic project.
3. For migration of tickets use the bull edit option in Jira. If you google it you will get to know more about bulk edit feature.

Hope this information will help you. Even I faced the same scenario and I was also pissed off. This feature is under development at the atlassian and it is been 2 years now. but there is no affirmative from Atlassian.

Mike_Illobre

@Amit Gaikwad thank you very much for the update and the information. Hope your doing well during these times.

Amit Gaikwad_92iuch

Hey @Mike_Illobre
I'm doing good I hope you are also taking care during this time. I'm glad the information is helpful to you.

unknown

This about sums it up.

Krista Delucchi_1v4h1a

I set up a ton of new projects as next-gen projects just now ahead of our jira migration to cloud so that we can utilize the new features of roadmap, but just realized I cannot assign a workflow. This is a problem and I can't change the project type to classic. This next-gen project type will only work for a few teams now because of this and they are teams I'm trying to get to stop using Jira because they constantly mess with our settings. Face palming really hard about the lost time I just threw at this.

Joey Triska

Really disappointed this isn't available yet, especially since the roadmap tool is gated behind next-gen projects. I know y'all probably have your hands full, but this is a really important feature to us, and based on the comments here, for a lot of other people, and it would be amazing if this could happen sometime soon.

Rakesh Kande_27a19q

any update on this? we want to add some new status to workflow but I don't see an option to do.

Jesse Geiger

For those awaiting a never-going-to-happen feature for Jira Next-Gen projects, the ability to customize your workflow AND the ability to control transitions, I suggest the following. Not super pretty, but definitely functional:

1- In your NextGen project, as others have suggested go to the BOARD section on the left and create all the workflow Statuses you desire (Blocked, Done, In Progress, QA, etc). Drag/Drop them in order from left > right in that board view. That will set the order they are displayed in the issue view, top to bottom.

2 - Go into the project's automation area (Project settings / Apps / Project Automation. Create a new rule and ensure it is set as a Project Rule, not Global. This most likely has to be set afterwards, but just to bring it to your attention.

3 - Create the rule as shown in the attached pic:
WHEN issue is transitioned from *current state* (pick one), and leave TO blank.
For CURRENT PROJECT (this makes it not Global)
Create a branch... IF {{fieldChange.toString}} DOES NOT EQUAL *State 2*
THEN Transition issue back to original state

This essentially forces transitions to follow a certain path using IF, THEN, ELSE logic. If you go from Analysis to QA, it will fail and transition back to Analysis. If you go from Analysis to Close, it could pass and stay there.

Create a new rule for each status, using standard logic to process (AND or OR conditions).

You can always throw an OR statement in there if you need to allow a transition to more than 1 other state.

This was a quick n dirty rule I made to get something working. I'm sure many of you will tweak it out to adjust to your environment.

Eugene Dementiev

Well, this is underwhelming. I have just created a Next-Gen project only to see that I can't change the workflow.

Fun fact: after deleting this project, I can't use the proper project name and project key for a new classic project, because the deleted project will still hold them for like 60 more days.

Not happy.

vampyren

Just noticed as well. Pretty bad user experience!

Jira is getting to big for its own good.

Embrenchia Snyman

Classic has roadmap now.

blim

Hello all,

We hope to deliver different workflows per issue type in the next couple of months.

We will be shipping multiple Done's statuses and the ability to map multiple statuses per column by the end of this month (Feb 2021).

We will follow up with:
1. Different workflow for epics
2. Ability to unmap statuses from the board
3. Different workflows per issue type

Feel free to follow this ticket https://jira.atlassian.com/browse/JSWCLOUD-17434 for updates.

Best,
Bryan Lim
Product Manager

Janice Warren

It appears that statuses and workflows may be edited now, if I am interpreting this correctly: https://confluence.atlassian.com/jirasoftwarecloud/manage-how-work-flows-in-your-next-gen-project-1005805102.html. I plan to test now. I want to use next gen roadmaps, but workflow inflexibility was a huge barrier.

yasmeen banu

I created a workflow for Team managed project and its in the inactive category as shown above. How do I use it for my project?

Arlene Zavala

Hello!

So Next-Gen projects do not allow you to associate the project to an existing Workflow. What you have to do is go to the Project > Project Settings> Boards> Manage Workflows> Edit Workflow>

This way you would need to add the Status first and Associate one another with the "Transition" option.

The "Allow issues in any status to move to this one" is setup by default, what I did was create the Transitions manually.

Hope this helps!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software

jira-cloud

agile

next-gen