Using SubQuery on Kanban Board to Exclude Work Items where FixVersion is Empty

[JD Lobue]

I am trying to use the subQuery filter on a kanban board to filter out all accepted work for only one column that is already released. Has anyone done this before or can someone lead me in the right direction?

[Nic Brough -Adaptavist-]

The sub-query on a Kanban board is there to define issues you do not want to see on the board because they're old, released and need no further action.

An easy definition of that is "they have a fix version set", but yours might be different.  

[JD Lobue]

yes, and I want to only do that for one of the columns. Can that be done?

[Nic Brough -Adaptavist-]

You can, indirectly, by saying "and status = (the status that is in the column)" in your filter.

But that kind of destroys the point of having a board, as you'll have to go search for and edit issues to get them to appear on the board again when you need them.

[JD Lobue]

That would not show me all the other items on the board. What I want is all the items in our other columns (To Do, In Progress, etc.) and only the accepted column to filter out fixVersion. What you suggest will not do that.

[Nic Brough -Adaptavist-]

Yes, that's why I said "kind of destroys the point of having a board".

I don't think the sub-query is the place to do what you are asking for here, I think you're going to need to do it with the board query, changing it to:  Show me (all the issues in all the columns *except* the accepted column) OR (issues that are in the accepted column AND have a fixversion)

Assuming the base of the board is just "project xyz", and your accepted column is mapped to the status "accepted" and no other status, then your board query should be

Project = XYZ and ( (status != accepted) OR (status = accepted AND fixversion is empty) )

[JD Lobue]

I don't think you are understanding what I'm asking, and I believe the answer is that subqueries do not handle this situation.

I want the board to still have it's own filter query and just the accepted column being further filtered differently. Doesn't sound like Atlassian can handle this. Thanks!