Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Cannot add issue types to a specific workflow scheme.

I seem to have a problem with one particular workflow, the one that has some 400 projects associated with it, of course.  

I need to assign a new issue type to this workflow scheme.  Yet I get the error message below, with the same issue ID regardless of which issue type I try to add. 

Also, when I am looking at "workflow schemes" there are some workflows that aren't associated with any issue types, because I deleted those issue types (e.g., we used to have a white papers issue type, which I've deleted because we don't use it anymore, which is still mapping to the whitepaper workflow).  

If I try going to "edit" to remove the issue types from the workflow scheme, they don't appear on that list. 

When I go to "workflows", the white paper workflow still appears as active and assigned to the malfunctioning workflow scheme, even though there are no projects using it.  

I do not have this problem with the other workflow schemes. 

Can this workflow scheme be fixed or is it just beyond repair?  Do I need to go rebuild it from scratch and associate all 400 projects with it one by one?

 

error screenshot.PNGdeleted issues still assigned to irrelevant workflows.PNG

2 answers

0 votes
Iago Docando
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 26, 2020 • edited

Can't you COPY the schema?? Then you'l find it under INACTIVE schemas at the bottom of the page and you should be able to edit it no problem since it is a new, unassociated, scheme. 

Then you'll have to manually assign the new schema, I'm afraid... Sadly, I don't think you can assign that new schema to each of your 400+ projects in bulk, at least not natively, but at least you can fix the errors. 

I can copy the scheme, but it copies the bug with it.  

Since posting this question, I have been in touch with Atlassian support, and they have confirmed that it is a known bug that happens if you delete an issue type without disassociating it from the workflow first.  

They are helping but it is requiring some effort as I have approximately zero coding experience. 

Iago Docando
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Oct 26, 2020

Sorry to hear that. I was hoping that maybe you coud edit the copy and just remove from the scheme the workflow associated to that deleted issuetype.

Best of luck.

Update: it turns out I cannot edit anything at all on this particular workflow scheme.  I tried to add a description (so people would know it wasn't working properly) but even trying to add something to description field returned the same error. 

Thanks Erica, I am having the same problem. If I understand correctly the workaroung is to create a brand new scheme?

Suggest an answer

Log in or Sign up to answer