Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue does not appear in jql results or dashboard

Sysad
Contributor
March 4, 2021

Hi

We are constantly seeing this issue where users run a defined JQL filter, for example, let's say Project=abc and staus!=closed and severity =high, and it should return 5 issues, instead, it returns 4.

The same happens in the two-dimensional dashboard gadget, where the total critical issue in the given JQL shows only 4 instead of 5.

To fix this, as soon as I run project reindexing, JQL results will be updated. We don't want to run full background reindexing because the application will not be accessible to users.

 

Is there a way to figure out the root cause?

2 answers

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 4, 2021

This suggests something is running which tries to set an issue status and either fails or does not index after doing it.

Do you have any scripts or automations that might be changing the status of issues?

Sysad
Contributor
March 4, 2021

Hi @Nic Brough -Adaptavist- 

Yes, we have a post function to update the status of a linked issue. Whenever the JSW issue is transitioned, its aligning JSD issue will be transitioned. Transitioning occurs across the workflow, from start to finish.

The issue of improper results is in issues of JSW and not for JSD.

Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 5, 2021

How are you triggering the transition of the other issues?  It sounds like you may be using a script that does not re-index after the transition somehow.

0 votes
Pavel Junek
Community Champion
March 4, 2021

Hi,

I'm afraid that won't be possible - the only chance to fix these problems is to perform a Full Reindex or Reindex from Scratch with a restart of Jira. I recommend running Full reindex outside working hours, eg overnight.

Pavel

Sysad
Contributor
March 4, 2021

@Pavel Junek 

Yup, looks like the only option. Will do that. Thanks for sharing your insights.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
VERSION
8.13
TAGS
AUG Leaders

Atlassian Community Events