Do agile workflows need to be updated on new versions?

We have serveral projects, and I can see the workflows below. It looks like the Agile version used at the time when the project was created is fix. Since OnDemand get's updated from time to time, the following questions come up:

  1. Do I need to update the workflow to the newest version?
  2. If yes, how to do it?
  3. If yes, how to know that I need to do it?
  4. How to know what changed?

I would like to have a gloabl standard workflow that's shared by all projects. So, change this one, changes everything. How can I do this? At the moment it looks like every project gets its own instance of the workflow.

Agile Simplified Workflow Scheme for Project FM
Generated by JIRA Agile version 6.3.6.1. This workflow scheme is managed internally by JIRA Agile. Do not manually modify this workflow scheme.
Agile Simplified Workflow Scheme for Project IN
Generated by JIRA Agile version 6.3.7. This workflow scheme is managed internally by JIRA Agile. Do not manually modify this workflow scheme.
Agile Simplified Workflow Scheme for Project NLPP
Generated by JIRA Agile version 6.3.5.3. This workflow scheme is managed internally by JIRA Agile. Do not manually modify this workflow scheme.

1 answer

0 vote

Well, you don't need to update anything if you're happy to leave them alone.

However, what's happening here is your projects are being created with a template that enables the "simplified workflow"

Each project that has this HAS to have a separate workflow - this is because the workflow is defined by the users (anyone with project admin) as they build their boards.

As a system admin, you can pull this from them and force them to use the same workflow - define a workflow, add it to a scheme, then apply that scheme to each project you want to force it on to. Their boards will stop defining the workflow when you do that (only admins can re-simplify them), and they'll need to map their boards on to your flow.

You don't need to use just one workflow or workflow scheme - you can still do things like "development project style 1, bugs handle one way, features another", "development project style 2 - all on one workflow", "operations project style" and so-on.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,308 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot