Can I move stories instead of subtasks on Kanban?

[CAMPO RAURICH Eduard]

I started to work with Kanban + Query swimlanes by priorities, but the team is used to working with subtasks. My goal is basically to have either:

- Only the stories shown, subtaks only when checking the details

- Allow the story to be moved through the columns, instead of the subtasks

So far I have tried multiple things with the same result:

- Edit filter to not show subtasks -> hides the parent stories, so only stories / defects without subtasks are displayed. I need the parents to appear anyway

- Edit main kanban filter to not show subtasks -> same behaviour, stories / defects that contain subtasks are hidden from the board

- Quick filter -> again, hides anything with subtasks 

I just need the parent to appear if the subtasks are filtered, I think that with that done It'll be good to go.

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

I think you should look at quick-filters on the boad.

Your board filter needs to include all the issue types you want to work with on the board, so you need to include the base issue types and the sub-tasks.

You can then use quickfilters like "issuetype in subtaskissuetypes()" or  "issuetype in subtaskissuetypes()" to show hide the parts you want to work with.

Jira can't do "only show me issues with no sub-tasks" though.  You could rig up an automation that picks up when an issue (of a sub-task type) is created, deleted, or moved to another parent issue and have it increment/decrement a "count" field on the parent.  Then you could use a quickfilter for " "issuetype in standardissuetypes() and count = 0"

[CAMPO RAURICH Eduard]

Hello, that is exactly what doesn't work:
- Board filter has stories, defects and subtasks
- Quick filter as such:

issuetype not in subTaskIssueTypes()

 - Board displays stories with subtasks, but can only move subtasks (this is what I want to avoid)
- When filter is active, board hides any stories that contain subtasks. Stories without subtasks remain on the board

This makes 0 sense, it's driving me crazy...

[John Funk]

Hi Campo - Welcome to the Atlassian Community!

Just hiding the sub-tasks should not hide their parents. 

Use something like Project = ABC and issueType != Sub-task ORDER BY Rank

and see what that gives you. 

[CAMPO RAURICH Eduard]

"Just hiding the sub-tasks should not hide their parents. "

And yet it does for me, I'm checking everything and still get the same results

[John Funk]

What type of project are you using? Company-managed? Team-managed? Jira Work Management/Business?

[CAMPO RAURICH Eduard]

Company-managed. If I have to ask for help on this, I don't know where the issue could be from our configuration as it does not seem logical to have this behaviour on Kanban

:(

[John Funk]

No, that doesn't seem logical. I would even go ahead and submit a support ticket for Atlassian to verify what is going on and if there is a bug that has been introduced. 

https://support.atlassian.com/contact/#/

[Sayed Bares [ServiceRocket]]

@CAMPO RAURICH Eduard what is the JQL query you are using in your filter?

If you change it to the following does it fix the issue?

project = ProjectKey and issuetype = story

[CAMPO RAURICH Eduard]

project = XXXXXX AND issuetype in (HU, HT, Incidencia) ORDER BY priority DESC, updated DESC

With this, any story / defect that has subtasks is just hidden from the board. I have checked also that it is not affected by the Kanban subfilter:

(fixVersion in unreleasedVersions() OR fixVersion is EMPTY)
AND (status not in (Closed, Implantada, Lista))

Which basically hides anything closed on the last column.