How can I map fields on a JSM project to a JWM project so data is preserved when moving an issue

Erick Armes

Our Marketing team uses a Jira Service Management project to field requests from fellow employees.  After triaging these requests, any that the team elects to action are 'moved' from the JSM project to the team's project, which is in Jira Work Management.  Despite setting up fields on the JWM project that mirror those in JSM, all data (other than summary) are dropped when moving the issue.  Any suggestions that would enable us to preserve data when moving between projects would be appreciated.

Mark Segall

Hi @Erick Armes - Based upon your description, I'm assuming that the JWM project is a Team Managed project.  These behave much differently than Company Managed projects.  Even though statuses and custom fields may share the same name as their company managed project counterpart, the backend IDs are going to be unique to the project.

You have two choices:

1. Create a new Company Managed JWM project and migrate the existing JWM issues to it.
2. Use automation to perform the "move" function which in reality would be cloning the issue to the JWM project and closing out the JSM project (you'll need Jira Admin rights to do this).

Option 2 would look something like this:

From Settings >> Global Automation

• TRIGGER: Manual
• ACTION: Clone Issue
  • Select the project
  • Select the issue type
  • Select the desired fields and set to copy from trigger issue

In the rule definition, you'll want to refine the project scope to the two projects.