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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Script Runner Issue Picker - Return a specific field of linked issue in JIRA export



I am using Script Runner Issue picker field to link one JIRA to another. Unfortunately in JIRA query exports, the issue picker field exports the linked JIRA issue key, which is meaningless for the reporting I need to do. I instead need it to export a different field on the linked JIRA (another company specific internal reference). Is this possible?


Thank you

2 answers

Hi Dan,

Thank you for your question.

I noticed you have tagged this question as for Jira Cloud but can confirm that ScriptRunner for Jira Cloud does not provide the same issue picker fields that the server version has.

I would advise re-tagging this question as Jira Server or reposting this so that someone more familiar with Jira server can see this and advise on your question.



Hi Kristian - oops, you are right - thank you, I have just updated the tags.

Hi Dan,

Currently, it is not possible yet.

There is a bug report filed for this issue in our support portal:

I would recommend for you to vote/comment on the bug report to raise its visibility to our developers.

Thank you for your understanding.

Kind Regards,

Hi Helmy,


Thanks for your reply. My use case/requirement is slightly different:

  1. Create a new JIRA project, TKT, with custom field "INTERNAL_ID" (text) and "related issue" (issue picker)
  2. Create two new JIRA tickets, TKT-1 and TKT-2
  3. Add "1234" to "INTERNAL_ID" on TKT-2
  4. Use the "related issue" field to associate TKT-2 onto TKT-1
  5. Create a search for issues which includes TKT-1 and the "related issue" custom field
  6. Export the search results to HTML
  7. Result: "TKT-2" is shown under the "related issue" column
  8. Requirement: "1234" (from custom field "INTERNAL_ID") is show under the "related issue" column

Looks like this requirement is also not currently covered, but please let me know if i'm in luck and it is?

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you