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; } } }

Use of "was in" operator

Leirbag Assuab

Hi,

This is embarrassing for me because maybe I'm doing something wrong and maybe it's obvious, but I'm not able to see it right now.

I execute this JQL below:

project = STS and created >= "2019/10/01" and created <= "2019/10/31" and assignee was in (e00002, a01559) order by key asc

It returns this issues list:

I execute another JQL, equivalent to prior one but with issue keys instead of created dates:

project = STS AND key >= STS-34490 AND key <= STS-36596 AND assignee was in (e00002, a01559) ORDER BY key ASC

It returns exactly same issues list:

But issue showed below (STS-34497) is not in the list and I can't figure out why. It seems that all JQL criteria is matched: project is ok, created date or issue key is included in interval searched, and user 'e00002' was assigned to this issue:

So, what is going on here? Am I doing something wrong? Perhaps I simply misunderstood use of "was in" operator? Or there's something more, like a bug in "was in" operator?

Our current version is 7.9.2 running over Oracle. I have successfully reindexed the instance but there aren't no changes in query results.

Please! Any help or suggestions?

Accepted answers

Ignacio Pulgar

Maybe the index is corrupted.

You may want to eliminate the index and build it again from scratch:

Shutdown JIRA
Delete all the contents from the following folder:
```
$JIRA_HOME\caches\indexes
```
Restart JIRA
Perform a full re-index

Hope it helps.

All comments

Ignacio Pulgar

Maybe the index is corrupted.

You may want to eliminate the index and build it again from scratch:

Shutdown JIRA
Delete all the contents from the following folder:
```
$JIRA_HOME\caches\indexes
```
Restart JIRA
Perform a full re-index

Hope it helps.

Tuncay Senturk _Snapbytes_

Hi @Leirbag Assuab

It seems to be a weird index problem.

First, I'd recommend to index the project which is the faster than the system wide reindexing.

On the other hand, you can check for other issues, and see whether it is related to the transition from Open to In progress. I faced some issues that the Re-index post function might cause such problems. Make sure that those post functions are seen within that transition.

Run Integrity checker, so that you make sure there is nothing wrong with the workflows.

Best

Leirbag Assuab

Thanks @Tuncay Senturk _Snapbytes_!

I performed full reindexing before posting but nothing changed.

I've checked all workflow transitions, it seems OK.

Integrity checker has completed with a full green.

I'll try to delete index files before reindeing as @Ignacio Pulgar suggests. I'll be back reporting about this

Best regards!

Tuncay Senturk _Snapbytes_

Do you see the same behaviour for other issues?

Leirbag Assuab

Yes! It seems generalized. JQL query returns about 50 rows. I've calculated they should be 100 or more.

I was suspecting about a JSU post-function, "update any field," where I update "assignee" to "%current_user%" just under certain issue fields conditions (this is because I can't use standard "change assignee to current user", I need a JSU pre-condition).

But I've seen issues returned by JQL where JSU post-function has been executed.

I don't see any common pattern in all issues not returned by JQL. It's really weird issue...

Leirbag Assuab

Hi @Ignacio Pulgar ! Thanks!

Your solution has worked! My JQL sentence is now returning all rows after rebuilding indexes from scratch.

I've fixed some workflow transitions before rebuilding indexes, as you and @Partibha Rani suggested. This should prevent errors in a future.

Thanks everyone for your support!

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-software

jira-software-server

jira-core

jql