How to set a board filter on AffectedVersion without filtering out sub-tasks in issue detail view

[Sian Hamer]

Using a single backlog for 2 teams, I'd like a board for each. However, if I filter on team (which is a label), I find that the sub-tasks are filtered out. (NB I don't want sub-tasks listed in the backlog, but do want to see them in the right hand panel - issue detail)

Currently what I see in the issue detail panel is 'sub-tasks being filtered by the board's saved filter'.

I cannot use any plugins, this needs to be done using 'standard' jql. Any suggestions?

[Taranjeet Singh]

@Sian Hamer Can you share your board's JQL filter? Are you using JIRA Cloud or Server?

What type of project are you using: Kanban or Scrum?

[Sian Hamer]

Hi, the project is scrum.

The board filter is very simple: project = GEN AND affectedVersion = "Phase Search" ORDER BY Rank ASC. It looks as if additional jql is needed to retrieve the subtasks. It seems the subtasks aren't logically assigned the same affectedVersion as the parent (which seems peculiar to me)

Using Jira Server 7.3.3

Thanks

[Taranjeet Singh]

@Sian Hamer Normally, I have not seen this issue. Based on your board filter, the issues and their sub-tasks should be displayed in issue detail view correctly.

Are you using "Affected Version/s" field separately for Sub-tasks as well?

[Sian Hamer]

hi again,

no, we are not using affected versions in sub-tasks  - these are all blank. 

[Sian Hamer]

Additionally, the epics panel is empty, and configuring 'show epic labels' has no effect - almost as if the extension of the query to select on 'Affected Versions'  - or indeed on any label - creates an unexpected limitation on the data returned.

[Taranjeet Singh]

@Sian Hamer I will not be able to provide much assistance without looking into your project and board settings. If possible and if you are willing, you can have a one-to-one troubleshooting session with me via a conferencing tool of your choice.

[Sian Hamer]

Hi, really sorry but I cannot do this. It is a client's jira. Thanks for your time.