<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=299788&amp;fmt=gif">

Bam! How to Pull Assets from One Jira Project into Another One

Atlassian, Jira

Untitled3

I have to say that we have some incredibly talented solution engineers on the Isos Technology team. Their ability to think far outside the box and make the unimaginable a reality is something I see on almost a daily basis. I've seen them do things in Jira that I never thought would be possible, like turning Jira projects into databases for other Jira projects to pull from.

While there are a few great asset management solutions for Jira on the Atlassian Marketplace like Insight for example, there are situations where you want to use the tools already installed on your instance or you just want to go 100% Jira native. In these cases, not only have we have found a solution, but we have also recently implemented it for a client. With just a couple of apps and some know-how to make it happen, we were able to build a complex database system that revolutionized how the client manages assets. We enabled them to quickly update their assets and work their tasks all in the same tool. 

 

Scenario 

In this example, we were building out an asset management system for an Operations Support team. We wanted to be able to track assets within Jira so that team members could find those assets using a field on other Jira issues. Also, when an asset was selected, we wanted to be able to pull in other data from that asset to the Jira issue. Examples of assets include hardware, vendors, applications, office equipment, products, etc. 

Screen Shot 2020-05-01 at 8.47.18 AM

 

Ingredients

Solution

First, we needed to create two Jira projects: the team Jira project to manage Issues and the database Jira project(s) to house the data used within the team's Jira project.

Pro-Tip

We created the database Jira project(s) under the Business project template to separate them from the rest and also assigned the Project Category: Database in order to further segment them from the other projects.

Next, we set up the Power Custom Fields used to select Issues from the database Jira project(s). In this example, we set up three fields:

  1. Hardware
  2. Office Equipment
  3. Software

These fields were added to the screens of our team Jira project, and they were plugged into our three database Jira projects in order to pull in the Summary field for each Issue within those projects.

Then we used Power Scripts to write an SIL script to allow those fields to pull the Summary field of each Issue into the team Jira project. Below is an example code snippet of what that script looked like.

KPOption[] options;
string[] issues = selectIssues("project = HARDWARE and issueType =\"Computers\"");
for(string issue in issues) {
    KPOption option;
    option.label = %issue%.summary;
    option.value = issue;
    options = addElement(options, option);
}
return options;

We will then assign this SIL script to the Power Custom Field(s) that we created within the field configuration screen.

 

BAM!

We now have ourselves a thriving asset management structure that can now be used across one to many Jira team projects.

If you're looking to explore this option and need some assistance, feel free to reach out! The Atlassian experts at Isos Technology are available anytime to walk you through this process.

Managing JIRA at Scale White Paper

TAGS: Atlassian, Jira

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Subscribe to Our Newsletter

Recent Blog Posts