Why Can't I set Component Value on Tickets?

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.

2 answers

1 accepted

3 votes
Answer accepted

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.

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.  

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 09, 2018 in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

375 views 6 0
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you