Love how Jira and Confluence continue to grow closer and better integrated. Thanks for continuing to perfect this inter-platform relationship... this is awesome!
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Thanks for sharing the article. The easier we can make release notes to actually make, I think the more enjoyable and therefore better & accurate they will become. Things like this are incredibly laborious for teams. If we make lives easier then it wont be such a burden for them.
We use a combo of Confluence and Jira in our team and let each do what it does the best (documentation in Confluence, epics/stories/RAID logs/etc.) in Jira.
We serve up a fair amount of Jira content in our Confluence space as we are trying to make it the single point to find anything related (be it in Jira, SharePoint, Teams, etc.) while not replicating Jira functionality in Confluence.
We also drive a fair amount of issue creation into Jira by employing Confiforms to capture the info in forms. auto-label/decision on issue type programmatically based on user choice and inputs and then IFTTT it into the appropriate project(s) as required.
Last one, which is a big one for me, drop Jira ticket references on Confluence pages (ideally in the section where it is relevant as opposed to the page level) and Confluence links in the Jira description/comments/etc.. This way it is simple mouse click to painlessly jump between the tools to find/update/understand by all team members.
61 comments