In an attempt to assign an issue type with a different workflow, I am posed with a problematic step in publishing the change where I need to associate statuses.
This is what happens: I am asked to associate new statuses to issue types that are not even part of the issue type scheme I am using. There are some issue types that are being used by JIRA in order projects and schemes, but not in My Service Desk Project. Although I see o (zero) issues depending on the re-association, I still have to go and pick new status for a very long list of issue types. That does not happen with other workflow re-assignments I do. This is puzzling me as I am afraid this is effectively affecting those issue types in other projects.
For example, Questionnaire, Portfolio Rebalancing, Wire Request SMS...Those issue types are not at all part of my issue type scheme.
I am clueless. Yelp!
It's a known annoyance or design failure in the "move" process. The screen lists all the potentially affected status no matter what, if there's might be a change needed.
You can completely ignore any line that says "0 issues affected". You will do no damage if you let them all "migrate" to the defaulted value, as no issues will be affected.
Just be very careful to check for all the non-zero results.
Yep, you were right. Clicking "associate" didn't kill my prod system...lol.
I wasn't happy with not knowing and researched, researched, then I finally researched.
Here's the answer: every issue type one is not using on a project will still get assigned by default to a workflow in your project as part of a group containing "all non assigned issue types" and precisely the workflow I was trying to replace hence the reason why i saw that during Publishing.
I tend to question JIRA more because it allows me to create custom field with the same display name of another one, which effectively broke another project some time ago. Obviously, someone was probably calling the display name of a field in code, but it was no excuse of JIRA forallowing me to do this in the system.
Anyway, appreciate the quick responses. Thank you for jumping in to help so quickly.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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