Pull field data from JS issue in JSM

[Nate Dickinson]

Is there a way to pull a field from a Jira issue into the description in JSM?  I have two projects. IGS is our JSM project, and IG is our Jira cloud software project. In IG I have screenshots stored in the functional field which I would like to share with the client making the request within the IGS JSM project. Is there a way to do this? 

I can pull a reference to another ticket outside of JSM, but I don't have the ability to define what is viewable in the JSM portal. 

[Mark Segall]

Hi @Nate Dickinson 

In IG I have screenshots stored in the functional field which I would like to share with the client

A couple questions on "Screenshots stored in the functional field"

• What is the "functional field"?  Is this a custom field?
• What do you mean by "screenshots stored in"...?  If your screenshots are attachments, they're simply attached to the issue, not a specific field.  Is this field providing a link to screenshots?

Answers to these questions will provide a better picture of your environment and will allow me to best answer your question.

[Nate Dickinson]

Functional is a custom field It takes all content types. I have my screenshots pasted into this field. 

[Mark Segall]

Thank you for the additional clarity.  So, am I understanding correctly that you are trying to make the attachments from the linked IG issue visible to the customer on the portal view?  

If so, this is unfortunately not possible (at least not natively).  You'll have two challenges:

1. Because IG is not a JSM project, you cannot surface any of the details about that issue.
2. You can use automation to copy pertinent information from the linked IG issue into the description of the JSM issue.  However, copying attachments from one issue to another is not currently possible (at least not natively)

There may be something in the marketplace, but I'm not aware of any apps off hand.

[Nate Dickinson]

That's what i figured. I hope they fix the attachments issue. That request has been out there for a while now with little movement. 

[Mark Segall]

Agree - I would love to see that addressed as well.  I've worked with a number of organizations that would love to have something like this.

A thought occurred to me since my last response depending upon data sensitivity of your attachments... An option could be to use Confluence as a source of truth for the content and simply link to Jira.  The confluence space visibility would need to be opened up, but then you'd use automation to copy the Confluence link rather than the attachment.  Of course, if you have strict or complex security requirements, this is not a good option.  However, I thought I'd throw it out there just in case.