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.
Hi Ryan,
By default in JIRA, the Epic Name only shows for issue type 'Epic', for other issues types as you know, we only can see the Epic Link in seaching. Here are two improvment tickets, which raised in our development projcet:
https://jira.atlassian.com/browse/GHS-8053
https://jira.atlassian.com/browse/GHS-8458
Please vote on it for implements and add to your watach list for future updates.
Ps: Here is the Implementation of New Features Policy
Cheers
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.