Hello there,
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.
Any guess?
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
https://www.youtube.com/watch?v=XKV-WA5RpD0
Cheers
Hello Vero,
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am looking to do the same thing. Is there a solution to this problem?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello, did you find a solution here? Looking for the same thing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.