I have two small problems that i am needing some help with.
These two issues are on separate projects and boards, but I am hoping you could help me to sort these issues out.
The first board is a Kanban board. You should go to board settings -> swimlanes and choose Stories. In this case subtasks will be under the parent.
I guess, the second board is a Scrum board. Subtasks are not visible in the Scrum boards in the Backlog view. But subtasks are visible in the Active Sprint view.
Sorry I was swamped with a new sprint... The one issue has been resolved but i am stilll having problems having my subtasks appearing on the Kanban board, the next issue after solving this was to get them to appear under their parent task, I can only test this once they appear.
The status of the subtask workflow are all in the columns on the board so i cant see why they are not appearing at all.
Thanks for the help
Have you checked that your filter is not restricting them?
Also, take a look at the workflow that the sub-tasks use and make sure they use the same statuses that are assigned to the columns of your Kanban board.
The 0 sub-tasks to parent is only for the subtasks currently on the board.
I am having this problem too and figured out it is because my filter was picking certain epics for the Kanban. Since sub-tasks do not technically have an epic link, they were not showing on the board. Now I have to figure out a way to filter by stories and their sub-tasks that are in certain epics.
I had this problem, and was hoping to use the JQL function parentEpic(), which is shown in the Atlassian support doc: https://support.atlassian.com/jira-core-cloud/docs/advanced-search-reference-jql-fields/
But parentEpic() is not a recognized function in JIRA at my company. Why is it in the Atlassian doc, but I can't use it?
The first part of my question was where we wanted the parent task to be a swimlane and the subtasks to show under them, which we configured under the board settings:
The second part was that the sub-tasks were being filtered out of the board, which we fixed using a better filtering technic:
Thanks for pointing that out, it is rather all over the place.
Thanks and Warmest Regards
I have the same problem on Jira Server. We move from Scrum to Kanban Mode and need a Kanban Board that works more or less identically to the Scrum Board. We have a filter that filters just for the project and want to use swimlanes for storys and all other issuetypes as we did before. So we set up the board filter, swimlanes by stories and mapped relevant statuses to columns, everything else is mapped to the kanban backlog. There are Tasks with subtasks that have statuses which are both mapped to columns on the kanban board.
And still not any single subtask is showing up! aaarrrgh - so frustrating!
When I try to debug the config and dive into the boardfilter via issue navigator, the list gives me every subtask as well. So I actually don't think that I need to include "issuetype in (standardIssueTypes(), subTaskIssueTypes())" into the filter. But even desperately did so to proceed with the problem. But we are still out of luck.
- so why are they broken for the swimlane view?
Thanks for quick reply
I'm struggling with the same problem. I have created a Board that contains the tickets for a subset of epics in the project, and I cannot get the subtasks to appear. I suspect that it is because subtasks do not contain an epic link. Instead, they are identified by and rely upon the link through their parent ticket. page_partain has aluded to this already. It seems to be a weakness in JIRA - I hestitate to say 'bug' because in reality, the filter is doing what it is asked and selects tickets which contains specific epic links. Using the extension issuetype in (standardIssueTypes(), subTaskIssueTypes()) has made no difference.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events