How can I move all issues from one project to another, ensuring an identifying component is set?

Question

I searched, didn't find a modern answer that was relevant.

I want to move all issues from project A to project B, in jira cloud, setting a Component value A to identify those issues in project B. Project B is not currently using any Components. I created an identical Component A in both projects, but if I try to bulk edit all tickets in project A, and edit, there is now way to bulk assign them to the Component A. If I bulk move them to project B, there is no way to ensure they are identified as Component A.

How can I move these tickets from project A to project B, and have them identified by a unique Component? Should I use labels instead?

Morgan

Morgan Fletcher_zajuf0 · Answer

How can I update these tickets in bulk edit, either before move to project B, or after? The field is not in the UX of the Bulk Change > Edit screen.

Morgan Fletcher_zajuf0 · Answer

I don't see the Component field in the UX of Bulk Change > Edit. This was my first thought, too. How do I do this bulk change to Components?

Morgan Fletcher_zajuf0 · Answer

I've created the Component A in both project A and B. I can't see the Component field in Bulk Change > Edit, in order to set it. I do not want to click through hundreds of issues to set it individually.