On my end, the user would want a similar setup, but instead, to DO see the subtasks of tickets each in the corresponding swimlane, e.g. the issue type story PROJ-2200 should have a separate swimlane for the story and then the sub-tasks need to go in that column. the story PROJ-2201 separate swimlane, and the subtasks.
How is this achievable?
If at all... @chercher @Dionei Piazza , got any idea, team? I will be very, very thankful!
Hi @Sonea
Yes, it is possible.
1 - Go to your board settings.
2 - Go to Swimlane.
3 - Create the master swimlane (where you don't want to see the subtasks).
2 - Below each master swimlane, create the swimlane details (where you want to see only the subtasks).
Master swimlane example: project = INV and issuetype in (Epic, bug, Story) ORDER BY priority DESC
Swimlane example detail: project = INV and issuetype in (subtask) ORDER BY priority DESC
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you! @Dionei Piazza
I might some more assistance.
I am on swimlanes and I see all our current existing swimlanes. With their JQL as well.
Are all of them currently master swimlanes?
One of our swimlanes at the moment should show subtasks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You're welcome @Sonea
Each configuration that you see is a swimlane.
So you just need to create a new swimlane to display your subtasks. In the JQL you will have something like this: issuetype = subtask.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, for example, I have the swimlane "Priority". And in tickets of that swimlane are sub tasks which I want to display in the swimlane Priority as well (below the main ticket/task). I don't want an extra swimlane just for subtasks. Just in my existing swimlane main tasks and their subtasks shown. :)
Thank you!! @Dionei Piazza
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sonea , so if you want to keep the current swimlane and also display subtasks below the main Tickets / Tasks, you will have to do two steps:
1 - In the existing swimlane, adjust the JQL filter so that it displays only the issuetypes "different" from subtasks. This would be the JQL snippet to be added to your filter (issuetype! = Subtask). Okay, here you keep a track only for the main items (epic, tasks, storys).
2 - Create a new swimlane where you will copy the same initial section of the previous filter, for example, priority = "Major". And it will combine this with a new snippet that JQL will bring only the subtask issuetypes. Then it will look something like this (priority = "Major" and issuetype! = Subtask). Ready! You now have a track /swimlane for the upper swimlane subtasks.
If you prefer, we can arrange a call to be more practical.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So I have two swimlanes but it displays only one? So in the view of active sprint there is only "priority" shown?
Priority--
Main Task 1
- Subtasks to main task 1
Main Task 2
- Subtasks to main task 2
Like this?
I am rather new to swimlanes and JQL so Im rather confused :P Thank you for your help!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey @Sonea
Add me dionei.piazza@gmail.com and lets try a hangout?
Sharing your board we can try to figure out this more faster, and then post the solution here to the community.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No problem @Sonea
Maybe you could take a screenshot of the configuration of your swimlanes and paste it here?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The JQL of the swimlane:
swimlane name: priority
project = JI AND issuetype in (Story, Task) AND component in ("Process - Archive", "Process - Management System") AND labels = priority AND text ~ Administration
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok @Sonea
This is your swimlane to show the Storys and Tasks issuetypes, and it's right!
Now you will need to create another swimlane to display the subtasks issuetypes. You can create the new swimlane this way:
project = JI AND issuetype = subtask AND component in ("Process - Archive", "Process - Management System") AND labels = priority AND text ~ Administration
So if you already have the subtasks created, and of course, substasks that respect the other filters (project = JI, component in, labels and text) of your JQL, they will appear on your board below the master swimlane.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So will it be like this:
main tasks (swimlane)
-- Main task 1
-- main task 2
sub tasks (swimlane)
-- sub task 1
-- sub task 2
OR
priorities (swimlane)
-- main task 1
--- sub tasks attached to main task 1
-- main task 2
--- sub tasks attached to main task 2
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Sonea
The first option would be more appropriate. And within each swimlane, create the other filters you need, such as priority, projects, etc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Sonea I'm afraid not, because JIRA can't know how to group and regroup the master/detail within the swimlanes. Maybe you will need to search for some plugin.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alright, because in a project I worked before, we had option one as default. We didn't set anything, it just showed us the sub-tasks to the tasks on the board. In my current project, it didn't so I was looking for a solution.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.