Exocet for Jira is now called Elements Copy & Sync. The name might have changed, but the people behind it remain the same. Learn more >
Keeping similar customer demands organised and associated when working in a multi-project JIRA environment can be quite a challenge. In this blog, we will show you how Exocet for JIRA can help you keep track of your linked issues by copying them from their original JIRA issue to a newly created one.
Let’s imagine you have a public JIRA project where customers can raise their demands and a private JIRA project used by your software development team. Your customers created a couple of demands in your public project, all related to the same core bug in your software.
In order to make it easier for you and your development team to keep track of these demands, you can create a new master public JIRA issue with all the essential information, before linking this master issue to each customer demand. With a single click from this issue Exocet can then create, in your private project, a new internal issue that will have the same summary, description and links to the customer demands as the master issue.
Let’s have a look at an example so you can better understand how Exocet can do this for you.
Creating your master public JIRA issue
This master issue in your public JIRA project will help you group all related customer demands in the same location. Create a new issue, add all the relevant information in the description field and create the links to each customer demand pointing to the same software bug.
We will use Exocet to create the new issue in our private project that will be used by our development team. Exocet will copy the summary, description and the customer issue links from our master JIRA issue. What’s more, we will use Exocet data panels to show additional information gathered from customer demands in our internal issue. This will be useful to our dev team or the product owner in resolving of the bug.
Let’s start by creating a field mapping to create the summary and a description field. The next step is to create a “Needs bug fix” Exocet operation that will use this field mapping. Since the new issue will be created in our private JIRA project, we will set our private project as a target project. In order to copy the links to the customer demands from an external to an internal issue, we will select the option “also copy JIRA issue links” and choose to copy all existing links.
In order to show additional information from external customer demands in our internal issue, we will add a data panel in Exocet, displaying only issues from our public project, and select the fields that we would like to display: issue key, summary, creation date, reporter and watchers.
Creating an internal issue with Exocet for JIRA
All we need to do in order to create our internal JIRA issue in our private project is to execute the previously configured Exocet operation from the master public issue by simply clicking on the “Needs bug fix” button. This is how the newly created internal issue looks:
As you can see, our internal issue created by Exocet incorporates all the important information from the external issues. This gives you and your team better insight into customer, as well as the need and tracking of all external demands from a single point.
And if you want to prevent the creation of duplicate issues in JIRA, check out Nicolas Simon’s article. Our consultant explains how nFeed can ease your team’s work!
And as we love to give more, with our latest version of Exocet you can also copy Confluence links from the source issue.