Our team has several specialists on it. Some are in Ops, other in QA, others in Development etc.
How can we separate out their work into different swimlanes? Currently swimlanes are restricted to be useful for being expedited or not. Any way we can make swimlanes more flexible?
Swim lanes just work off JQL.
Do you use the component field to categorise your issues as OPs/QA/Development. If so, you can add a swim lane per component (with the jql checking for the component value) if you want and name it appropriately.
Similarly you could use labels rather than compoent.
Tnx – but in addition to that, another problem arise …
I can now group UserStories with Swimlanes based on Epics like that, but if a UserStories have sub-tasks, the subtasks are not properly grouped to UserStories.
I tried following JQL – and it works
"Epic Link" = "NHATA-9" or (type = "Story / Task" AND (parent = "NHATA-2" or parent ="NHATA-14"))
Where 9 is an Epic, and 2 and 14 are UserStories. But this means that for every sprint I have to write/connect those UserStories to the Epics manually.
Now I read that there are some plugins for that but we are using the onDemand version so I can’t go for that.
Do you know a way to solve this dynamically in a onDemand version?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Community! me again 🙂 If you’re a marketing team using Confluence, we want to hear your story! How did you start using Confluence? What are your use cases? What have been some of the benefits?...
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