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
Status | ||||
---|---|---|---|---|
|
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}
Code Block |
---|
{
"fields": {
"customfield_cfid": option.id // number, taken from allowedValues
}
}
|
MULTI_SELECT
filter through allowedValues and extract all option ids of interest
Code Block |
---|
{
"fields": {
"customfield_cfid": [...options]
}
}
|
SAMPLE_FOR_BOTH
Code Block |
---|
{
"fields": {
"customfield_10148": 7,
"customfield_10136": [3, 10]
}
} |
Status | ||||
---|---|---|---|---|
|
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
Status | ||||
---|---|---|---|---|
|
It is possible to use Advanced Issue Links in Automation for Jira.
single select fields
Code Block |
---|
{
2 "fields": {
3 "customfield_10148": {{triggerIssue.fields.customfield_10148.id}}
4 }
5} |
multi select fields
Code Block |
---|
{
2 "fields": {
3 "customfield_10136": {{ triggerIssue.fields.customfield_10136.id.asJsonArray }}
4 }
5} |
additional info:
customfield_10148
id of a single select AdvancedIssueLinks fieldcustomfield_10136
id of a multi select AIL fieldtriggerIssue
is the issue that triggered the automation, assuming this is in a branch rule
Status | ||||
---|---|---|---|---|
|
...
Dec 22, 2023
Updated Forge node.js runtime
Significantly improved the performance of the app
Added default link type for inline linking in Issue Panel
May 26, 2023
Added manage:jira-project to scopes
May 21, 2023
Removed JSM support for custom fields
Info |
---|
After carefully reviewing the situation and collaborating closely with the Atlassian team, we temporarily removed the JSM scope for Linksy. This means you can now use Linksy without needing a JSM license, but linking issues directly from the portal won't be possible. We understand the importance of accessibility and ensuring a seamless user experience for our customers. Therefore, we are actively working alongside Atlassian to find a more comprehensive and permanent solution that aligns with their recommendations and our commitment to providing you with the best possible product. We are very sorry for any confusion or inconvenience caused during this process. We value your feedback and appreciate your patience as we resolve this issue. We aim to provide you with a reliable and hassle-free LInksy experience. |
March 20, 2023 Feature release
Linksy custom fields are now available for use in a JSM portal request form.
Using Custom Fields on a JSM portal
March 15, 2023 - Bugfix
Fixed an issue where Resync would sync only one issue link per field.
→ resync will now sync all issues matching the JQL and link type of the field
March 14, 2023 - Initial release
Two custom fields
Sync issues with Jira links
Linked Issue details panel
Issue link resync
Multiple contexts per field