Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation doesn't show embedded description

Tiia Ojanaho
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 15, 2025

We use Jira Product Discovery to prepare changes and create delivery tasks to development project using embedded description

Once the delivery ticket is Done, we have an automation that sends a notification to our Slack channel. The problem is that it only shows the Jira Product Discovery idea link instead of the content. 

<{{issue.url}}|{{issue.key}} {{issue.summary}}> has been published.
{{issue.description.abbreviate(500)}} 

Results in:

[Link to delivery task that works fine] has been published.
[https://company.atlassian.net/jira/polaris/projects/T5S/ideas/view/447127?selectedIssue=T5S-161%7Chttps://company.atlassian.net/jira/polaris/projects/T5S/ideas/view/447127?selectedIssue=T5S-161%7Csmart-embed ]

Any suggestions how I could show the description from the embedded JPD idea instead?

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 15, 2025

Hi @Tiia Ojanaho -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

  • an image of your complete automation rule in a single image for continuity
  • an image of the rule details at the top of the rule
  • images of any relevant actions / conditions / branches
  • an image of the audit log details showing the rule execution

Until we see those...

Let's assume you are trigging the rule when the delivery work item (in a software project) transitions to Done, and that work item is linked to one-and-only-one JPD Idea.

That work item has a special link to the JPD Idea: "implements".  But unfortunately that link type can be used for other things.  The workaround is to use the internal name for that link type: "Polaris issue link".

This expression would find the linked JPD idea, returning its key and summary:

{{#issue.issuelinks}}{{#if(equals(type.name, "Polaris issue link"))}}{{outwardIssue.key}} -- {{outwardIssue.fields.summary}}{{/}}{{/}}

How that works is:

 

To learn more about the internals of work item smart values (and so build your own expressions like this), please see this how-to article for finding the smart values supported by rules: 

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

 

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events