Expand/collapse subtasks is missing from the backlog of a company-managed JSW SCRUM board

Question

Hi all, I've been trying to find answers about this issue all day and have had no luck.

My problem is that the expand/collapse carets do not appear next to Story issues that have subtasks. This is in the backlog view of a specific SCRUM board on a company-managed JSW project.

In other SCRUM boards in company-managed JSW projects, also in the backlog view, the expand/collapse carets do appear next to Stories that have subtasks, so I know this feature is generally working on our site.

When comparing the project with the problem to a project without the problem, all of the settings seem to be exactly the same except for one. The filter for the problem board includes issues from two different projects where the boards that work only contain one.

The two projects included in the filter on the problem board are both company-managed JSW SCRUM, however.

I'm keen to hear if anyone has any insight into what's causing this issue on this particular board.

Trudy P Claspill · Answer

The carets are missing for all issues, including those in OPTAMAP.

If you run the filter directly in the View All Issues screen, do you get any subtasks listed in the results at all?

I found another option that might work.

Instead of using "Epic Link" try using "linkedIssue"

https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#linkedissue

When that is used it appears to get both the direct child of the Epic and subtasks under that child.

I tried that myself with this short query:

project=CS or linkedIssue=CS-9

Epic CS-9 has a child in the CK project, and that child has a subtask.

I saw expand/collapse carets for all issues that had "not done" subtasks, including the CK issue.

Note that if all the subtasks are already marked as "done" and the parent issue is in the Backlog section of the Backlog screen, then no caret will show. "done" issues are not shown in the Backlog section of the Backlog screen. And by "done" I mean in a status that is mapped to the right-most column of the board.

Laura Rusenstrom · Answer

Hi Trudy, thanks for the response.

The carets are missing for all issues, including those in OPTAMAP.

It's unfortunate that subtasks are treated that way. The inability to nest Tasks under Stories means we have no choice but to use Subtasks, which have a bunch of limitations built into them already. I guess this is another one. Kind of limits the system's flexibility for different work styles.

Trudy P Claspill · Answer

The way the filter is written

1. You will get all issues from the OPTAMAP project

2. Plus you will get the direct child issues of the Epics you called out, regardless of what project they are in.

3. You will not get the subtasks under the child issues of those Epics, unless the child issue and subtasks are in the OPTAMAP project.

If Epic OPTAMAP-1 had a child issue in Project X you will get only the child issue, not it's subtasks.

Are the carets missing only for issues pulled in from the other project?