Hey folks, we are JUST getting started with confluence/jira. We're looking to create our requirements in Confluence and then link them to Epics in JIRA. Basically 1 confluence page will = 1 epic. The confluence page could contain many requirements, which will ultimately be linked to individual Jira Stories. (In theory, anyway.)
The thing is, using the default requirements template in confluence, the automated requirements numbering (REQ-001, REQ-002) does not allow for any nesting of requirements, like this:
1.0 This a concept
1.1 This a specific requirement about that concept
1.2 This is another specific requirement about that concept
2.0 This is a different concept.
So two questions:
1. Is there any way for confluence to allow nesting of requirements like that in an automated fashion? Sort of like MS word when you create an outline, if you are at 1.0 and hit right tab, it becomes 1.1?
2. Is there any way to change the default requirement number generator? So instead of REQ-001, we could make it start at, say, just 0001?
As I understand it, you are asking if you can change the way the issue keys are generated? If that is what you are asking, then no. Issue keys are are always generated in the form of PROJECTKEY-XXX where XXX starts at 1 and increments up by one with each issue created.
Hope this helps.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
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