Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Changing a workflow will modify also the one whom it was copied from Edited

Given the following scenario:

  • I had to assign a new workflow for story issue type on a specific project which was part of a workflow-scheme with another 10 projects.
  • I created a new workflow-scheme and added a new, modified workflow for story (which is a copy of the old story workflow).
  • The changes for the new story workflow were renaming some statuses and changing several transitions.
  • I switched my project to the new workflow-scheme.

Now the issues appeared, I observed that the old workflow for story, which is no longer assigned to my project, is modified. I did some testing and every time I modify one of the workflows, the other one gets modified as well, but in a different way. 

Anyone has seen this odd behavior before?

Jira version 8.13.6

1 answer

1 vote

Hi, @pbasarab !

Renaming statuses is bad idea because they are global items.

If you need a different statuses in different workflows - you should use existing ones or create a new statuses.

Hi,
Indeed, renaming was a bad idea. I just needed the order to be changed between them, so I played with drag and dropping the transitions, which did the trick. 
Didn't think renaming will trigger such odd behaviors (and I guess it should not???).

Like John Funk likes this
Daniel Ebers Community Leader May 08, 2021

Unfortunately, this is just like Alexander stated - a basic design circumstance.
In case you won't be able to tell the name of the previous status name you can probably reconstruct it by looking into Auditing.

Apart from that, like Alexander said, you would need to create new statuses given the old naming is not the desired result (f.e. not the status names you want to have).

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase

The benefits of using Jira in different departments

Jira is a great tool to use across different departments. Forget that paperwork – switch to Jira and get that tasks done smoothly. Marketing Jira allows for a complete digital transformation of you...

126 views 0 7
Read article

Community Events

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

Events near you