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
Our team is trying to be more transparent with our customers and expose the work we are doing so we don't have to answer questions about what's coming next. We use Jira Software and Confluence. The plan right now is to setup a Confluence page with sections for Next Release, In Progress and Coming Soon.
I want these sections to use the Jira macro and pull the tickets from Jira so it's automated. I don't want to manually key these into the Confluence page.
Has anyone else done something similar and do you have any suggestions on this current approach or possibly and completely different approach?
PS: I'm looking at setting up custom fields for the issue key and summary so these can be exposed in Confluence instead of the actual key and summary fields since these would be inaccessible links for our customers. The values of the custom fields are not showing yet. I read some posts where others had this issue and one user said it took a little while but finally showed up.
For this You need to integrate Jira and confluence using application link
Then you can use the Jira Issue macro which allow you to fetch and display the filter issues on confluence page. Refer this Document
If you dont want to exposer the issue key and summary then you can remove that field from macro and put the custom field which you have this details
For this you can write the automation rule which will copy the issue key and summary to another custom field which you can display in confluence page
Accept the answer if it helps
We struggled to keep the manually maintained roadmap in our documentation up to date, which inspired us to build a solution for public roadmaps.
We are now starting a private beta and would love to get your feedback.
For more information and to sign up for the beta, take a look at https://www.released.so/roadmaps