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 :
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 .
If "Block" is in the target workflow, then it's not an "illegal" status, it's valid.
You have two options
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 ?)
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.
...It's true that there are projects in Jira; but they are merely a way to cut off issues, to tell them apart from other sections of work and to apply rules that are specific to that team (the schemes)....
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