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; } } }

Issues are pointing to old version of Workflow

Ron Judenberg_li9wat

I have modified the workflow for all types.

Some of my older issues will not allow me to use the transitions I have defined, but rather are giving me only the options from previous versions of the workflow.

Does anyone know how to get them to "see" the new workflow?

Accepted answers

All comments

Mikael Sandberg

Hi @Ron Judenberg,

Welcome to Atlassian Community!

When you created the new version of your workflow, did you do that from a copy of the existing one or did you make your changes directly in it? If the latter, try and make a copy of your current workflow, rename it, and then go to your workflow scheme and replace the existing workflow with the new copy.

Jack Brickey

Additionally it doesn’t really make sense that some older issues work one way while newer issues work a different way. More likely the situation is that you have different issuetypes and different workflows associated to those issuetypes. Go to project settings > workflows and check what workflows you have associated to which issuetypes. And make sure that you have the desired workflows associated to those issuetypes.

Joseph Chung Yin

In addition to what Mikael and Jack mentioned, you should also check if your "older issues" is in the same project where you have applied/published the new WF or not. It is because each project can have its own custom WF scheme. Therefore, you will need to update the appropriate WF scheme to utilize your new WF design too.

Best, Joseph

Ron Judenberg_li9wat

This is a Team-managed Project. I don't have the ability to have multiple schemes unless I transition it to a Company-managed Projec

Daniel Ebers

Hi @Ron Judenberg

so we learned the problem is happening with in one team-managed project, for the same issue type across all issues and there is no difference in affected issues, just probably their age.

I am wondering if this is happening for other users (and/or on a different PC, perhaps a different browser) as well.

In other words: all issues configured so they have the same workflow there should be not difference be visible in workflow's behaviour, just depending on the issue's age. This is why I think this could be a client related problem (browser foremost).

Regards,
Daniel

Nick

I'm also seeing this issue - I changed workflow and mapped all issue types to the new flow.

Now I'm finding issues still with the old workflow attached, but Project settings shows that those issue types are clearly mapped to the new flow.

Nick

Ug, found that the board was missing a Project filter. Nothing to see here...

Sahar Aliabbasi

can you explain what you did to fix this? I updated my existing workflow (no copies) and now I find my old issues are not able to move through this new existing workflow. All issues (old and new) are linked to the same updated workflow. Can't figure this out still

Welcome!

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

Quick Links

Find more posts tagged with

cloud

workflow

jira-service-management-cloud

jira-service-management