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.
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 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,
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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!
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