Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

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

Erick Armes
Contributor
February 1, 2023

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.

3 answers

1 accepted

2 votes
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 1, 2023

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.

0 votes
Erick Armes
Contributor
February 1, 2023

@Joseph Chung Yin @Mark Segall - thank you both.  I suspected this might be the case.  I have come to appreciate the Team Managed projects (despite the lack of shared objects), so I'll give Option 2 a shot.

0 votes
Joseph Chung Yin
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 1, 2023

@Erick Armes -

I agreed with what @Mark Segall suggested, one drawback of Team Managed project is that their custom fields are not shared and only local for the project, thus it will not carry over during a issue move operation.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events