nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Help with Automation across JPD and Jira

Sandy Kim_denfi0

Hello Atlassian Community,

I found a post that is very similar to the issue I am facing, with regards to writing automation across Jira and JPD. The example that I read that was very close to my scenario is

Solved: Automation Help - Copying Target Start from a JPD ...

except that I was looking for automation to flow from Jira FixVersion into Target Release field (which I believe is a ?custom field. Not sure). FixVersion is an open text field and Target Release is a drop-down, which I can configure to have the same pre-populated list that matches FixVersion in Jira. Otherwise, I can use Requested Delivery Timeline (short text field).

I need guidance on how to write the automation rule, namely the smart value string for the value to land in either field.

I appreciate any help.

Accepted answers

Marc -Devoteam-

Hi @Sandy Kim

The Fix Version description can be fetched via a smart value in Jira automation.

But the Fix Version description can't be updated via automation, this can be done via the GUI or the API.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-id-put

But can you describe what you exactly would like to happen?

All comments

A A Ron Geister _Trundl_

@Sandy Kim

Good day to you Sandy. Here are some of the smart values that are available for versions:

{{issue.fixVersions.name}}: Returns the name of a fix version.
{{issue.fixVersions.description}}: Returns the description of a fix version.
{{issue.fixVersions.releaseDate}}: Returns the release date of a fix version.
{{#issue.fixVersions}}name:{{name}};released={{released}};id:{{id}}{{^last}},{{/}}{{/}}: Iterates through all fix versions and extracts their name, released status, and ID.

{{version}}: This smart value is used when you need to refer to a specific version (not a fix version for an issue).

{{version.name}}: Returns the name of the version.
{{version.description}}: Returns the description of the version.
{{version.released}}: Returns true if the version is released, false otherwise.
{{version.releaseDate}}: Returns the release date of the version.
{{issue.Target end}}. Target release Eample in use:
{{issue.resolutiondate.diff(issue.Target end.toDate("yyyy-MM-dd")).prettyPrint}}

Here is a link to the available support document https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--version--

I would say it would be nice to see a screenshot of what you have today so we can help provide more details around what might need to be fixed or changed.

Sandy Kim_denfi0

Audit Log.png

Sandy Kim_denfi0

Hi Aaron. Thanks for replying. I pasted screenshots of the audit log and automation rule. I think I messed it up because it's not working.

Marc -Devoteam-

Hi @Sandy Kim

The Fix Version description can be fetched via a smart value in Jira automation.

But the Fix Version description can't be updated via automation, this can be done via the GUI or the API.

https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-version-id-put

But can you describe what you exactly would like to happen?

Sandy Kim_denfi0

Hi Marc,

Thanks for responding. I'm looking to keep the JPD project in sync with the corresponding Jira project. We're using JPD to be purely customer-facing so whenever the Product Owner updates the FixVersion on any issue, it will automatically update the Target Release field in JPD.

Is this achievable using smart values alone? Was hoping to do this without needing to bring in one of my developers.

Thanks,

Sandy

Marc -Devoteam-

Hi @Sandy Kim

I read that the "Target Release" field is a drop-down, what are the drop down values?

So if the "fix version" field changes the Target Release needs to be updated, to what?

The fix version description you mean is just text set to a version number, this is not a change of the fix version.

A A Ron Geister _Trundl_

@Sandy Kim

I believe you can take the smart value and add it to the field itself so if you want the value on Target Release just put the smart value {{issue.fixVersion.description}} in the box value for Target Release. That should work as long as the value is readable to the value in the box.

Sandy Kim_denfi0

Hi Marc,

I want to have the values match in Target Release and Fix Version. Tried the smart value but not yielding results.

My screenshot provided is an old one. Kindly disregard.

Sandy Kim_denfi0

Thank you for jumping in to help. I have tried your suggestions but it's not working for me but that's ok. I'll escalate to tech support now.