We're using the orderly database for managing metadata attached to the Epics we're closing as a company. When we close an epic, we store the information related to that epic in a Confluence page. The orderly database sits on that page and contains information such as the "Project Name", the "Epic Close Date" as well as the "Epic Title".
We've discovered a great automation between JIRA and Confluence that allows us to automatically create that Confluence page when we add the Epic in JIRA.
To make this a truly awesome sync, it would be amazing to have the epic populate the Orderly database with the fields from that the epic. This means the team create the epic in JIRA and part of the page creation and metadata management can be actioned from one place. Having it update bi-directionally would be a nice-to-have but the type of metadata we're managing really only needs to be created once.
It would allow those great JIRA-confluence links like "mentioned on" to help people navigate easily between those two places.
Here's hoping that Atlassian with solve this stuff with the new Confluence Database!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.