You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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
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
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.