nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

JQL query doesn't return any Sub-task issues

Petr Michna

Hello,
one of our customer report weird behavior of JQL.

Usually they used following JQL query:

project = XXX AND issueType = Sub-task

This stopped working, result of search is empty screen.

If they used JQL query:

project = XXX AND issueType in (subTaskIssueTypes())

They get list with Sub-task issues.

I've checked that "Sub-task" is right name of sub-task issue type.

I saw this problem in past but I don't remember how we solved it.

I tried to re-index project and also whole JIRA, put there copy of workflow but without success.

Any idea how to fix it?

Thanks

Petr

Accepted answers

thalesc

Hello Petr, I faced a similar issue the other day and I think I know the reason.
You said:

in this JIRA instance are 2 similar sub-task issue types ("Sub-task" and "Sub-Task"). Their project has just "Sub-task" sub-tasks issue type.

This basically means they have the same name (if you ignore the case). Try changing the name of one of them (put an underscore in the end or something) and you will be able to get results again.

After that figure out a way to move all "Sub-task" to "Sub-Task" (or vice-versa) and remove the duplicated one.

It looks like jira cannot handle two issue types with the same name when you are filtering by the "duplicated" issue type in the JQL.

All comments

Nic Brough -Adaptavist-

That sounds like someone renamed Sub-task so the search does not find it any more.

Have you tried retyping the JQL and accepting the auto-suggestion it makes as you type sub-task ?

Petr Michna

Hi Nic,

in this JIRA instance are 2 similar sub-task issue types ("Sub-task" and "Sub-Task"). Their project has just "Sub-task" sub-tasks issue type. There wasn't any change with issue types in project settings. There was just modification of workflow, but it is mapped for right issue types.

If I use Basic search query, I got exclamation mark if I want to select "Sub-Task" issue type, If I use "Sub-task" it is OK.....but without any result (it should return more than 2000 issues). Same if I use auto-suggestion in advance search.

Regards
Petr

Nic Brough -Adaptavist-

That suggests you haven't got any "Sub-task" issues defined. Could you pick one of the 2000 issues you say it should be showing and look at the project and issue type?

thalesc

Hello Petr, I faced a similar issue the other day and I think I know the reason.
You said:

in this JIRA instance are 2 similar sub-task issue types ("Sub-task" and "Sub-Task"). Their project has just "Sub-task" sub-tasks issue type.

This basically means they have the same name (if you ignore the case). Try changing the name of one of them (put an underscore in the end or something) and you will be able to get results again.

After that figure out a way to move all "Sub-task" to "Sub-Task" (or vice-versa) and remove the duplicated one.

It looks like jira cannot handle two issue types with the same name when you are filtering by the "duplicated" issue type in the JQL.

Petr Michna

Hello Thales,
thanks for suggestion, it looks that it solved problem. But I'm still wondering if it is root cause of problem. JIRA let you create Sub-task and Sub-Task issue types, so I would suppose that also searching for those issue types will work. Also customer use this issue type ("Sub-task") for long time and this search problem happend last week. So it had to work before.
Anyway thanks for your help, we will ask other users to move their Sub-Task issues on Sub-task issue type.

Regards
Petr

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server