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
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
What I have:
What I am trying to do:
To perform this, I use:
Well, this is not rocket science and works fine. But... all the body formats of the Confluence page content include html tags. And html does not render in JIRA text fields for security purpose. Since the Confluence and JIRA editors are the same, is there a way to push the content into the JIRA issue description in a way that it will render correctly for most of the Confluence tags (headings, colors, etc...) ?
The only solution I currently see is to use a converter between html and JIRA wiki markups, but this is quite tricky and cannot be performed in the cloud environnement.
Note: I could also use JIRA Cloud scriptrunner to any means.
Hi @Cédric Cox
Look at this post, maybe can help you
Inside there is a video
Thank you for the tip. However, this allows me to do the oposite of what I am trying to perform. Our single source of truth is Confluence, as indicated in the video. Despite the fact that the jira filter macro is very usefull to link the two products, it does not help me to fill the issue description with the confluence page content, as all I get is a link to confluence.
The idea is to avoid dev to go to confluence to get the information, and stay in JIRA to do their job.