Changelog

This page includes release notes and updates for both Trophies for Jira and Confluence. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from our apps.

Go to our JSM support page to ask questions, report bugs or suggest new features.

15 December 2021

NEW Issue update with API

In order to update with REST API, they need to do a couple of steps:

  • get issue editmeta /rest/api/3/issue/{issue.key}/editmeta

  • find custom field that they’re trying to edit

SINGLE_SELECT

find in allowedValues of that custom field object option where value contains issue key, value is {issue.key} {issue.summary}

1 2 3 4 5 { "fields": { "customfield_cfid": option.id // number, taken from allowedValues } }

MULTI_SELECT

filter through allowedValues and extract all option ids of interest

1 2 3 4 5 { "fields": { "customfield_cfid": [...options] } }

SAMPLE_FOR_BOTH

1 2 3 4 5 6 { "fields": { "customfield_10148": 7, "customfield_10136": [3, 10] } }

 

Custom field links are now clickable in the old issue view. Due to Atlassian limitations, links in the new issue view are currently not supported. https://jira.atlassian.com/browse/JRACLOUD-77848

 

It is possible to use Advanced Issue Links in Automation for Jira.

single select fields

1 2 3 4 5 { 2 "fields": { 3 "customfield_10148": {{triggerIssue.fields.customfield_10148.id}} 4 } 5}

multi select fields

1 2 3 4 5 { 2 "fields": { 3 "customfield_10136": {{ triggerIssue.fields.customfield_10136.id.asJsonArray }} 4 } 5}

additional info:

  • customfield_10148 id of a single select AdvancedIssueLinks field

  • customfield_10136 id of a multi select AIL field

  • triggerIssue is the issue that triggered the automation, assuming this is in a branch rule