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

how to bring in a field from Jira

Sue Hannan
Contributor
November 20, 2024

I am trying to bring a value in from jira that is a single select field. I want to get the value from the jira ticket that I am linking.

2 answers

1 accepted

1 vote
Answer accepted
Nick Haller
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 21, 2024

Hi @Sue Hannan ,

It's my understanding when a JPD idea is linked to a Jira issue, you want to copy the Jira issue's single-select field into the JPD idea's single-select field. If there is more to this use case like if this is through deliveries or something else, please share whenever you have the chance.

One issue I could see happening is dependent on where the linking occurs - meaning if the Jira issue is linked within the JPD idea, or if the JPD idea is linked within the Jira issue. To account for this, I configured an IF/ELSE automation that can work for either. It might look something like the one below.

The first half of this automation (IF) accounts for when a Jira issue is linked within a JPD idea:

ssa1.jpg

1) WHEN: Issue Linked (All types in this example, but can be configured to your use case)

2) IF/ELSE: Conditions

  • Project = select JPD project

3) BRANCH rule / related issues

  • Type of related issues = Current issue (which is the JPD idea)

4) THEN: Edit issue field

  • Select JPD single-select field
  • Use smart value: {{destinationIssue.customfield_12345}}

 

The second half of this automation (ELSE) accounts for when a JPD idea is linked within a Jira issue:

ssa2.jpg

5) ELSE-if: Conditions

  • Project = select Jira project

6) BRANCH rule / related issues

  • Type of related issues = Linked issues (which is the Jira issue)

7) THEN: Edit issue field

  • Select JPD single-select field
  • Use smart value: {{triggerIssue.customfield_12345}}

 

A few things to note about the automation above:

  • IF the first half of this automation does not match, then it will review the ELSE second half. IF the first half of this automation matches, then it will not review the ELSE second half
  • customfield_12345 should be replaced with the ID of your Jira single-select field's ID. You can find this using this page: Find my custom field ID number in Jira
  • As mentioned above, depending on where the linking occurs would determine whether to use destinationIssue or triggerIssue in the smart value.
  • The Scope of this automation is set to Multiple projects with only the JPD and Jira projects select, but can be configured depending on your use case
  • An automation cannot create new options/values, so these need to exist within your JPD single-select field beforehand

 

Hope that helps and doesn't overcomplicate things, but again - just trying to account all variables, and where the linking occurs. Let us know if you have any questions.

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 23, 2024

Hi @Sue Hannan 

What problem are you trying to solve by doing this?  That is, "why do this?"  Knowing that may help the community to offer better suggestions.

For example, for an Idea in JPD, are you trying to make a field visible from an issue linked as a "delivery ticket" to help coordinate with the Idea's progress?  To initialize an Idea field? And so forth...

Kind regards,

Bill

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events