Im new to JIRA admin and having trouble deciding the best structure for my project.
Components needed and how they are currently worked;
This structure will then need to replicate for each release;
In my mind the flow would be as follows;
But Jira cannot handle a forth sub level.
Could anybody suggest an alternative that Jira would accept?
Take a look at this (https://confluence.atlassian.com/display/JIRAKB/Using+JIRA+for+Helpdesk+or+Support).
Quote (currently assigned as subtask)
Buddy Test (currenty assigned as subtasks)
All these can be sub/issue types. You can use Issue Links to link issues together.
A way to provide bugs for these new features over 40+ clients
Issue security scheme to handle issues for different users/groups.
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