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

Why Can't I set Component Value on Tickets?

Kathy Watters

We have been using a component value on our tickets for a project. Yesterday I moved the tickets to a new project. Now, there are no values showing up for Component and when I go into edit mode for a ticket and choose "Component", I see the word "None" with no opportunity to edit the value.

Accepted answers

Nic Brough -Adaptavist-

Components belong to projects, so when you move an issue from one project to another, the components have to change (usually deleted). It will preserve them if you have the same named components in the target, but you have to make sure they are there before you move.

Also, not having defined the project component list is why you can't edit the "none" - there's nothing to change the value too yet.

All your moved issues will have a note of what component(s) were removed in the move in their history.

All comments

Sten Sundelin

Did you check the list of components on the target project? If this is not set up, the values would be cleared when you move the issues.

Nic Brough -Adaptavist-

Also, not having defined the project component list is why you can't edit the "none" - there's nothing to change the value too yet.

All your moved issues will have a note of what component(s) were removed in the move in their history.

Kathy Watters

Thank you! That is exactly what happened. The component values weren't set up for the project before tickets were moved. Hopefully this answer will be helpful to another new JIRA user.

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

jira-core