Release automation with rich text

[Pablo Botas]

Hi experts! We are sending automatic Slack messages when a new version is released with something similar to this:

Hi team!! New version <https://company.atlassian.net/projects/XXX/versions/{{version}}/tab/release-report-all-issues|{{version.name}}> was released on {{version.releaseDate.mediumDate}}. Nice work!

Release description: {{version.description}}

Please, ask any questions in this thread :point_down:

However, now there is a rich text field replacing the description as the main description of the release in the UI. How could we use data in that field? See the following image for clarity

[Lionel Rudaz]

Hey folks, 

I'm running into a similar problem, even though I want to post the same field this time in Teams.

At the end of the day, it's hard to catch up where to fill up the release notes. When I mean release notes, it's not just a list of issues. That, I know how to do thanks to this question on the forum 

We'd like to avoid as we can copy and paste and simply have one place where we write a clean release notes that we can then convey to different tools. Notify the staff in Teams, annotate Mixpanel, etc.

Let me know if you need more details, but that would be extremely useful to be able to get this new rich field in the automations.

Thanks in advance

[Bill Sheboy]

Hi @Pablo Botas 

Are you asking: how can the markup in the field be used the Slack message?

That may not be possible unless the markup syntax is the same.  Automation rules do not have built-in translations to other markups.  If the syntax is simple, you could try using the replace() or replaceAll() functions to perform the translation.

Kind regards,
Bill

[Pablo Botas]

Thanks Bill! Yes, not worried now about how to actually make it look nice in Slack, although that'd be the ultimate goal. So far I could not find the data field that needs to be used to get the rich text (although maybe with a different markup) to Slack.

[Bill Sheboy]

Thanks for clarifying...

There have been a couple of other questions / posts asking this, and I believe those new  release section fields are not available to the public REST API functions yet, and so they are also not available to automation rules.

[Murat Seven]

Hi @Pablo Botas 

Could you please provide more details about your specific use case? Additionally, could you include a screenshot about your rich text field? I attempted to use your context, but I did not observe any rich text in the version section.

Are you referring to the description field in an issue?

 

[Pablo Botas]

Yes Murat, I have edited the question and added a screenshot. The description in your screenshot is ok, I can get it to slack, but there is this new rich text section that I don't know how to access