We'd like to streamline our process for writing user stories for fixed-price/scope projects. Let me explain how we are doing it:
The easiest way is to use the JIRA macro in Confluence.
The typical way to handle this is to create the JIRA stories from your Confluence requirements page, as you mentioned. At this point, I remove the table and replace it with the JIRA macro using a JQL search to display the relevant stories. You can customize the macro to show any field, such as the estimates that you mentioned.
This doesn't provide the Confluence-JIRA update that you were asking for, but it puts your JIRA stories one click away for easy update inside Confluence.
Any update in JIRA will be reflected in the Confluence JIRA Macro.
Thanks for your answer Sebastien.
Unfortunatley this doesn't quite work for us, because you cannot comment on the issues in the JIRA macro in Confluence. The idea of having the issues in Confluence is to be able to hold a discussion with the client in order to finalise the acceptance criteria.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs