nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do I add a custom field to the "Update Fields" screen that is displayed when I convert a sub-task to an issue?

Patrick Schulz

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?

Accepted answers

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.

All comments

Nic Brough -Adaptavist-

Make sure the field is valid for the target issue type.

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.

Patrick Schulz

It is. At least when I create a new issue of type story i see the field, so I assume it is valid.

Jobin Kuruvilla [Adaptavist]

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.

Patrick Schulz

It did not solve me the issue, but the answer is nevertheless correct.

Patrick Schulz

Thanks Joachen, it made the trick for me. I removed the field from any kind of sub-tasks (there it is useless) and suddenly the field appears.

Patrick Schulz

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration