Component field can't be edited

When I move issues from one project to another, the JIRA system field "component" doesn't transfer into the target project, and I can't edit that field. I didn't think there were field-level security mechanisms in place in JIRA, and I can't find where to enable that field's use.

Any suggestions?

2 answers

Do you have different screens / field configurations in use in your target project? And for the field "content": Every project has its own components. Movin a field to another project doesn't add the component to the component list of your target project.

"Component" appears to be a JIRA system field, not a custom field - so that field exists across all projects.

It is a system field but the values are project specific

0 votes

Component is a system field, and the list of them is project specific. You need to make sure component is valid in the target project (check the field configuration, and then if it's on at least the "view" screen - these won't stop it moving if they are not set, but they will hide it from you). Then, you need to make sure the component exists with the same name in both source and target projects, before you move the issues,

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,707 views 17 21
Read article

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