Component field can't be edited

[Lee Correll]

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?

[Nic Brough -Adaptavist-]

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,

[Christian Czaia [Decadis AG]]

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.

[Lee Correll]

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

[Christian Czaia [Decadis AG]]

https://confluence.atlassian.com/display/JIRA/Defining+a+Component

[Christian Czaia [Decadis AG]]

It is a system field but the values are project specific