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; } } }

Confusing messages when moving/converting from one Issue type to another

Katie Elliott

I'm converting between 2 issue types using "move". The message (screenshot below) indicates there is a way to update fields in those issues or to select Retain to keep the values. I don't see a way to select Retain.

Also, I don't understand why it is only showing one field (a field we don't use and haven't customized or differentiated between the issue types) rather than the many other fields that ARE different between these two types.

Move Issue.png

Thanks

Accepted answers

All comments

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

Move will automatically retain values for fields if the field is valid in the target project and has the same context.

It will drop any values if a field is not present in the target project/issue type.

It is asking you to give it a Story point field because that field is required in the target project.

Katie Elliott

How can you tell when a field is required by a project/issue type? It's a move within a single project--I'm just moving an issue from one type to another type. We don't use Story points at our company, but maybe it's somehow required by a mistake (some jira default?) somewhere that can be fixed?

Nic Brough -Adaptavist-

You have to look at the field configuration for the project.

Katie Elliott

ok thank you

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud