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.
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 email@example.com with anything you're hoping to see in next-gen workflows.
@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 [ firstname.lastname@example.org ] 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.
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".
It wouldn't be so bad if the next-gen workflow was even remotely useful; but (sub)tasks go straight from Open to Done, which is kinda mad. The general Agile way of doing things, we do work on Tasks (which show up as sub-tasks) in Jira, and so time tracking and status really belong on tasks, not stories. A story is considered Accepted/Done once all tasks are done and the work is accepted by the product owner.
It's shocking that in 2019, Jira STILL doesn't have a workflow that can model BASIC agile workflow that has been documented and well understood for almost two decades.
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.
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):
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:
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.
Hey @QueenElizabeth !
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.
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!
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 : 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.
This works to get the issues over, but then you change all of the keys and numbers on the tickets which is a problem if you're integrated with other systems or referencing tickets all over other tools like my co. Thank goodness I realized this wouldn't work before I moved a ton of tickets to next-gen.
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.
Hey Next-gen fans, Would you like the opportunity to give direct feedback to the Next-gen product team? Would you like the chance to preview and test new Next-gen features? I’m excited to annou...
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