When I convert a sub-task to an issue, the "convert sub task" wizard starts.
In the first step I choose the issue type (story in my case), the second step is skipped and the third step "Update fields" already shows me some fields (the fields displayed vary depending on the issue type).
How do I add another custom field to this screen?
As far as I know only fields that are not configured in the source project s fieldconfiguration but are configured in the target s fieldconfiguration appear in that mask.
I think if you want to update other fields you have to create some kind of workflow transition.
If you make the field mandatory on the taget issue type and the field is absent on the sub-task, you will be asked for it in the "update fields" screen. If the field is not mandatory, JIRA assumes that you just want to move only the existing fields.
"Update fields" screen only shows the fields that needs changes due to one reason or the other.
Yes, you are right, mandatory fields are allways displayed there if they were absent on the other issue type they become displayed. Thanks for this additional information. But making the field mandatory is not an option for me, bacause it must be possible to leave it empty. But nevertheless, the answer is correct.
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