Unable to extract smart value for a custom field

[Parikshit Ghosh]

Hi, 

I'm trying to automate release notes into a slack channel and have followed the steps provided on this thread.

However I'm unable to extract the value stored on a custom field (multi line text) "Release Notes".
Tried all of the below combination of smart values that I gathered from various sources and couldn't get it to work. 

{{release notes}} ;
{{customfield_11300}};
{{issue.fields.release notes}};
{{issue.fields.releasenotes}};
{{issue.releasenotes}}
{release.notes}};
{{issue.release notes.description}}
{{issue.customfield_11300.value}};
{{issue.description}}
{{issue.Release Notes}} ;
{{issue.customfield_11300.value}};
{{issue.customfield_11300.description}}; 
{{issue.release notes.description}};
{{issue.release.notes.description}};
{{issue.release notes.description}}

Thanks in advance for the help.

[Daniel Eads · Accepted solution]

Hi @Parikshit Ghosh ,

For multiline text fields, the description and value functions don't actually print text. Calling the field alone (with no function at the end) should. I see you've tried {{issue.Release Notes}}, which I would expect to work. These functions should all work with a multiline text field:

{{issue.Release Notes}}
{{issue.Release Notes.body}}
{{issue.Release Notes.text}}

I would specifically recommend trying with the .text function since you're pushing into Slack. We have seen some instances where the wiki renderer being enabled on a field (instead of the Default text renderer) has messed up some of the formatting as a field gets sent to Slack, since Jira's wiki markup and Slack's messaging format are different.

If that still doesn't get the field body into Slack, it would be helpful to see a screenshot of the rule you currently have configured and a screenshot of the Release Notes field on the Jira issue you're testing with.

Cheers,
Daniel | Atlassian Support

[Parikshit Ghosh]

Thanks Daniel for your prompt response. 

I've tried the suggested smart values and still no luck. 

Please see attached screenshots for reference. 

Cheers,

Ghosh

[Bill Sheboy]

Hi @Parikshit Ghosh 

The issue you are seeing is that Lookup Issues only supports a subset of the issue fields, and your custom field is not one of them.

If you have the same value in all the issues, you could:

• pick one issue and branch to it with JQL
• capture the Release Notes data using a Created Variable action
• use that created variable to show the data in the message

Best regards,
Bill

[Parikshit Ghosh]

Thanks @Bill Sheboy  for your suggestion. 
I was able to make this work by simply adding a branch and not so much by having to create a variable action.

Although I've managed to retrieve relevant custom field values from the related stories linked to the version triggering the automation, I've got a couple other questions to try and iron out as part of the automation rule.

1. I'm able to add images to the release notes custom field(multi line text), however I'm unable to preview this image in slack. 
Workaround: Generated an image url link from slack and added that into the Jira field, which again doesn't provide a preview in the message itself but can be viewed upon a single click. 

2. Audit log is producing "some errors", although I'm receiving a successful message in slack.  
I've got Jira administrator access 

Added screenshots for reference. 

Thanks again. 
Ghosh

[Bill Sheboy]

Hi @Parikshit Ghosh 

I do not know how to solve that image preview issue between Jira and Slack.

Regarding that error message, that would seem to indicate the custom field name does not match the definition: releasenotes perhaps versus "release notes".  Do you see the same error if you run that JQL stand-alone in advanced search?

[Anand Inamdar_Amoeboids]

@Parikshit Ghosh if you are open to using an app to do this stuff more easily you may want to look at Automated release notes for Jira. There is free as well as paid version of the app on Jira cloud.

Disclaimer: I am the product owner of this ARN app.

Best,
Anand

[Bill Sheboy]

Hi @Anand Inamdar_Amoeboids 

When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see:

Atlassian Community online guidelines for Marketplace and Solution Partners

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Atlassian-Community-online-guidelines-for-Marketplace-and/ba-p/689723

Best regards,
Bill

[Anand Inamdar_Amoeboids]

Thanks for the nudge @Bill Sheboy just updated the response.