Convert sub task to issue

gilles kekenbosch

I have a few questions with convert sub task to issue

First of all, if the status of the source subtask exists in the target workflow, the step of defining the target status is skipped, whereas it is possible that it has to be changed.

Secondly, I don't understand how the fields to be configured are selected in the next step: they are neither all the fields nor all the mandatory fields in the target type nor anything I can think of.

Thirdly, as there is no constraint on the fields that are mandatory in the target, the resulting issue is likely to be badly initialized. Some mandatory fields may not be editable in the target status if they are hidden or read-only.

Finally, I support the request for adding a permission to run this function which is currently not considered by Atlassian, since, for the captioned reason it is best to restrict it to user with administration rights.

Nic Brough -Adaptavist-

I do not understand what you are asking about here.

>if the status of the source subtask exists in the target workflow, the step of defining the target status is skipped, whereas it is possible that it has to be changed.

I cannot work out what you are talking about here, other than it's something about the relationship a sub-task has with it's parent and their status.  All I can tell you is that the status of parent and child are technically totally independent, but most of us do some restriction of transitions, most commonly "cannot close issue while there are open sub-tasks"

>I don't understand how the fields to be configured are selected in the next step: they are neither all the fields nor all the mandatory fields in the target type nor anything I can think of.

What "next step"?  You've not said what you are doing.

Fields are made mandatory in field configuration for the issue type.  They're not flagged as such during any process other than "edit field config"

>as there is no constraint on the fields that are mandatory in the target, the resulting issue is likely to be badly initialized.

See the bit above about field configuration

>Some mandatory fields may not be editable in the target status if they are hidden or read-only.

Jira doesn't do field level permissions, you can either edit an issue or you can not.

>I support the request for adding a permission to run this function

What function?  You have not told us what you are talking about