Is there a way to pull the value from a Software Project into JPD ticket?
Asked by Louise Baker:

In our software Jira projects, we have two fields for Versions: the default Fix Version (which we update when the ticket is closed) and a custom "Target Version" (which we use to indicate what release a ticket SHOULD be done in).  

I'd like to pull one or both of these values INTO a field in our JPD project, so users can see when to expect an idea they have planned.  

I tried to accomplish this with Automation, but didn't quite get it right, so I gave up.  

Any one have success doing something like this?


Answers:
author: Nick H
body: Hi [@Louise Baker](/t5/user/viewprofilepage/user-id/4751632) ,

We've found an automation like this one below works well when trying to map Jira delivery fields back to the linked JPD idea when the delivery is updated:

![auto1.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/327263i8973D499B6B33989/image-size/large?v=v2&px=999 "auto1.jpeg")

* WHEN: Value changes for Jira delivery field(s)
  * Select the delivery field(s)
    * In the example above, the automation is monitoring the *Customer Name (Jira)* field

<!-- -->

* BRANCH: Branch rule / related issues
  * Type of related issues = Linked issues
  * Link types = Implements

<!-- -->

* THEN: Edit issue fields
  * Select the JPD idea field(s)
    * In the example above, the automation is monitoring the *Customer Name - JPD (JPD)* field
    * NOTE this is copying the *Customer Name (Jira)* field from the **Trigger issue**

We would suggest the field-types match 1-to-1 - meaning:

* If your Jira field is a numbers fields, the JPD field should be a numbers fields
* If your Jira field is a single-select field, the JPD field should be a single-select field
* etc.

\^ Otherwise you may encounter problems and errors with the automation.

You can also use [Smart values](https://support.atlassian.com/cloud-automation/docs/smart-values-in-jira-automation/) to insert data into the JPD field as well so you do not necessarily need to copy the Jira field exactly - making it more flexible.

Hope that helps!!

comments: author: Louise Baker
body: Thanks! This is helpful. I am having issues using the trigger parent field, as since its a "Version" field, there is not a corresponding field in JPD. I believe that's the root of the issue I first experienced, and your message here helped me realize why I am having that issue.  
Thanks! :)  

<br />


author: Nick H
body: It *may* still be possible, but I think will depend on how your "Version" field is being parsed.

I don't believe my Jira instance has a "Version" field specifically, but does have a Fix Version field which I'm assuming might be similar.

When using the [Get Issue API](https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-issueidorkey-get) on a Jira issue that has the Fix Version field configured, I noticed it's an array:

![auto2.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/327272iB4656CDFC6CACA2C/image-size/large?v=v2&px=999 "auto2.jpeg")

I know the Labels field is also an array field - so I configured a similar automation (to what I previously shared), and used a [Smart value](https://support.atlassian.com/cloud-automation/docs/smart-values-in-jira-automation/) to enter the Fix Version value into the Label field of the idea:

![auto3.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/327273i0E018E55780F88DB/image-size/large?v=v2&px=999 "auto3.jpeg")

![auto4.jpeg](https://community.atlassian.com/t5/image/serverpage/image-id/327274i1EAE359BB760C5AB/image-size/large?v=v2&px=999 "auto4.jpeg")

```
{{triggerIssue.fixVersions.name}}
```


author: Louise Baker
body: Thank you!! I'm getting a little closer. Had it fail, but I'll keep poking. THanks so much


author: Anthony C
body: Hi Nick, a question for you if I may ask: in your opinion, theoretically I should be able to pull a JPD issue fields into a Jira Work Management or a Jira Software issue fields right? (I am trying to use multiple JPD projects that can be overseen in a high level Jira Work Management project).


author: Nick H
body: Hi [@Anthony C](/t5/user/viewprofilepage/user-id/5496415) ,

Yes, it should be possible (through automation) to pull JPD fields into a Jira and/or JWM fields.

Are you facing and issues trying to do so?


author: Anthony C
body: Hi [@Nick H](/t5/user/viewprofilepage/user-id/130772)

I am simply new to the Atlassian world, and when I asked some of your colleagues how I can get a portfolio view of separate JPD projects (separate because I am being asked to keep info from the each individual projects separate from the users of the other JPD projects), I was told that that was not possible.  

I haven't had a chance to play with the automations but will do so later today! I assume I can only pull fields that are common between the 2 project types (JPD vs Jira Software or Jira Work Management - so I wouldn't be able to pull a custom formula field from JOD into a number field in Jira Work Management right?  

I was looking at JXL.app in the Jira Marketplace, or simply opening a Jira Software or a Jira Work Management project and pulling in issues from various JPD projects, however maybe I will need to use automations to pull the fields I want.  

<br />


author: Bill Sheboy
body: Hi [@Louise Baker](/t5/user/viewprofilepage/user-id/4751632)

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas. Thanks!

Until we see those...

Please see this question from yesterday which seems quite similar to yours. I added some suggestions to that one for how to get the data from the "Delivery Tickets" to the JPD idea.

<https://community.atlassian.com/t5/Jira-questions/Jira-automation-rule-to-update-fixversion-of-JPD-ticket/qaq-p/2713241>

Kind regards,  
Bill

comments: author: Louise Baker
body: Thanks for your response - however I don't have an automation to show as i couldn't ever get it to work, so I simply deleted the step :)  

I"ll update the main column to include the custom field names though.. maybe that might help?


author: Bill Sheboy
body: Please review that other post, as it outlines what is needed to sync this field between the projects, including:

* adding the custom fields to the JPD project
* making the rule global, or multiple-project in scope
* accessing the issues by the links, such as "implements" and "is implemented by" depending upon the direction
* deciding what to do when there are multiple Delivery Tickets, each with potentially multiple values in the Fix Version field

Also please note: this information could be the *names of the versions*, but it will not be the actual versions in the implementation project.


author: Louise Baker
body: Hi Bill - Sorry for the delay. Here is the full workflow:

![Screenshot 2024-06-04 at 4.33.51?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/327903i4AC3FF878D299B63/image-size/large?v=v2&px=999 "Screenshot 2024-06-04 at 4.33.51?PM.png")

For that last step, that's where I"m having issues. For JPD, I tried a Single Select at first, which was obviously wrong as Fix Versions can be multi select. I then tried multi-select field in JPD project, and still nada. Finally, I gave up and just did a short text, which fills it, but unideal as I'd rather it be an option that can be filtered on. oh well.  
![Screenshot 2024-06-04 at 4.33.58?PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/327904i6C2179CA74D14CAB/image-size/large?v=v2&px=999 "Screenshot 2024-06-04 at 4.33.58?PM.png")

If thetrigger issue has Fix Version of 9.1, then the new custom field in JPD's value is \[9.1\].  
Likewise, if its 9.1 and 9.3, then the value in JPD is \[9.1,9.3\]  
I can't get it to display w/o the \[ \] wrap.

Lastly, the error I'm getting when the custom field is not a text (but is a multi-select field type) is:  
Error editing issues  
IDEA-180 (Specify the value for Version Released in an array (Version Released))


author: Nick H
body: Hi [@Louise Baker](/t5/user/viewprofilepage/user-id/4751632) ,

Mapping to single/multi-select fields is a bit tricky. As far as I know - Automations do not have the functionality to create new values/options within one of these field-types.

Unless the value/option (9.1, 9.3, etc.) already exists within these field-types when mapping via automation, you will face errors like the one you mentioned.

It *may* be possible through an [API request](https://community.atlassian.com/t5/Jira-questions/Add-values-to-select-list-via-automation/qaq-p/1995363), but not through the method you shared.

As for extracting the value within \[ \] , try something like this using [string processing](https://support.atlassian.com/jira-service-management-cloud/docs/string-processing-methods/):

```
{{triggerIssue.fixVersions.name.substringBetween("[","]")}}
```


author: Louise Baker
body: Thank you Nick! I'm glad to know it wasn't a "me" issue and just a limitation. Appreciate all the help you and Bill have given!