Problem in Issue Navigator (Jira v5.2.4)

I have found that the issue navigator is reporting a wrong status for an issue, i.e., the issue screen shows status A while Issue navigator shows B.

This seems to be caused when you use post-functions in a workflow. In my case I have a scriptrunner and a 3rdparty plugin.

After rebuilding the indexes for the instance, in one case the status is shown OK, but in another it does not change unless you edit the issue.

Is this a known bug? Fixes?

Thank you!

2 answers

1 accepted

1 votes

It's not a bug in the navigator - the navigator uses the index to read it's data from, whereas the issue view screen uses the database.

What's happened is your index is not being updated, so it's drifted away from the database.

The usual culprit is pretty much what you've guessed:

  • A post function is updating data after the issue has been indexed (check the order of post functions on your transitions).
  • Or, a post-function or listener needs to re-index the issue explicitly and is not doing it.

Your 3rd party plugin may be the culprit, or your script, but that's where the "bug" is.

A post function is updating data after the issue has been indexed (check the order of post functions on your transitions).

I double checked this and the reindex is always performed after any custom postfunction

Or, a post-function or listener needs to re-index the issue explicitly and is not doing it.

According to this KB , after Jira 5.1 indexing has changed for workflows transitions and plugins should not worry abou it. In particular I have a scriptrunner script that creates issues B from issue A, but issue A status is wrong in the Navigator after the transition for issue A workflow.

Yes, 5.1 improved it, so there's less need to explicitly re-index, but the symptoms you are seeing are very clear - it is not being done when it needs to be

You need to isolate which post-function is causing the problem and work out why it's not re-indexing.

Ah, excellent! Interesting issue with the plugin - if you don't mind, could you tell us which one it was, so we can point other people at it if they run into it?

I had not noticed this warning from the plugin site:

Due to indexing changes in JIRA 5.1, this post-function should be placed immediate after the function: Re-index an issue to keep indexes in sync with the database. If you don't do this, the parent issue will not be indexed correctly.

Now the status shown is correct. Thank you!

Ah, that makes sense - it's very powerful, but with the post-functions, a lot of users don't grasp that they need to explicitly re-index when using it.

Actually I did not explicitly reindex in the script. I just moved the postfunction after the Re-Index following the above warning and it works. Before it was before the Re-index and did not.

Hi,

I'm having trouble with this same re-index issue in a JIRA 5.2.4 instance. My custom post-function is placed two steps above the default re-index post-function, and I've made sure that it throws no exceptions, but still the default re-index doesn't work. This is a screenshot of my list of post-functions for a specific transition; the custom post-function is circled in red:

problem_function.jpg

 

What I still haven't got to understand is, in which way a custom post-function can disable or block a further execution of the explicit re-index function? Even the "update change history" function is executed correctly, so why only the re-index function is affected, unless the custom post-function is placed below it?

Thanks,

GERMAN

 

 

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,876 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot