How can I control Jira "convert to issue" operation ?

Hi ,

Today  user can convert sub task issue to any type (from example from sub task to Bug) , which is OK .

My problem is start when issue move to "illegal" state on the new issue type.

Example from what it happen to me :

  1. User created sub task - status New 
  2. User promote sub task from New --> Block (till here all ok)
  3. User "convert to issue" to Story type 
  4. I reach illegal status - Story is in Block status while in Story workflow you can reach Block only from State A / B . As Story didn`t reach to Block from A / B status . Bug is "stuck" and no "workflow" option available 
  5. Be advise that Block is valid status in Story but only from specific statuses 

Same can be happen also when I will use Jira "Move" option and change issue type.

How can I force issue to be created in New status when issue type is change (and not to move with current status) ? is it configurable via jira / do I need add-on for it ?

Will be happy to get suggestions .

Thanks 

1 answer

0 vote

If "Block" is in the target workflow, then it's not an "illegal" status, it's valid.

You have two options

  1. Remove "Block" from the target workflow.  Users will be forced to select a valid status when they change the issue type
  2. If you can't move the converted issue to a new status, then your workflow is broken - you should change that so it does have an outgoing transition the users can use.

If you have ScriptRunner or a bit of coding time, you could protect the transition with a condition like "only if issue type used to be a sub-task type"

Thanks for your fast answer , I wants to clarify my problem .

Block is valid status in Story workflow but not from all states. 

In sub task - user can move sub task from New to Block while in Story there is no transition from New to Block But the option in Jira "convert to issue" cause that sub task moved to Story issue and its status is Block (and previous status) is New and this bring me to "broken workflow" as you mention.

 

How I can control / protect the transition ? it not pass via my workflow ? (or maybe it is ? and I can add some validation in my workflow ?) 

 

Ofira

I understood the situation fine, but I think I missed a point in the beginning of my answer.  You can not do anything about the conversion process.  There is nothing wrong with it as far as the data is concerned - an issue is in "block", the status is there in the new workflow, so changing the type and keeping the status is perfectly valid and the right thing to do.

The "change issue type" thing is not a transition, it is a structural change to an issue's settings, and has nothing to do with the workflow.

My suggestion was that you allow people to move blocked issues to a new "correct" status, and protect the transition so that it's only used at the right time.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Sarah Schuster
Posted Mar 28, 2018 in Jira Software

Can a company’s culture make or break agile adoption?

Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...

12,709 views 15 13
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