Can I map custom fields when moving an issue to a different project?

In Project A, I have a field called QB ID. In Project B, there's a field called External ID. Is there any way to map the fields so that when a user moves an issue from one project to another, any value that was in QB ID will automatically transfer to External ID? I'm an administrator, so I do have access to the workflow, if this is something that can be set up there.

1 answer

1 accepted

0 votes

Not in the UI. Simply put, the fields are separate, Jira has no way of knowing that you might want to do this, or have any code to support it.

Of course, you can deal with it with a bit of code. If you find/write a "listener", you can write code to say "on MOVE event, read QB off the issue and add it to External". I'd recommend a look at the script runner plugin to do this.

Thanks, that's what I was afraid of. I'll look into script runner, but my company is pretty new to Jira. What kind of language does script runner use? Where can I find examples of the kind of listener I'd need?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,042 views 13 18
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot