Re-index automatically after changing issue status

[Simon G_]

Hi!

I have problem: I have different Issue status between the view issue screen and the issue navigator.

I found this KB dealing about this problem: https://confluence.atlassian.com/display/JIRAKB/Different+Issue+Status+between+the+View+Issue+Screen+and+the+Issue+Navigator

Indeed, I have an automatic rule which change the status which change the status triggered on a new comment. The rule work fine but I have to run a re-index so the status on the two pages still the same.

How can I do a re-index in the same time of my new comment rule?

Thanks.

[Simon G_ · Accepted solution]

In fact, it seems that the probleme came from my mail handler: my Jira mail handler and my JSD mail handler were configured on the same pop account. Indeed, the problem appears only when customer or agent responding by mail.

It seems to be good now.

Thanks!

[Nic Brough -Adaptavist-]

As standard JIRA + Service Desk will always index an issue when it is changed, the question becomes "how are you implementing your automatic rule?"

[Simon G_]

Hi Nic,

You are probably right but I don't know where is my mistake.

Here is my in my workflow the transition "Respond to support/customer", both are same and are in the default value:

http://hpics.li/bf5e51b (sorry for the external link, I don't know why I have an error when uploading image today)

Then here is my rule changing the status:

http://hpics.li/95a4395

[Nic Brough -Adaptavist-]

That looks like it might be the automation add-on doing it - can you confirm that?

[Simon G_]

Nic, I have installed Jira Automation Add on, but it seems this add on doesn't propose to reindex. See the action proposed: http://hpics.li/bbddc6f Maybe another solution would be to reindex my issues every few minutes?

[Nic Brough -Adaptavist-]

The problem is that the automation plugin is triggering transitions, it's not changing things outside JIRA. Transitions index the issues, so you should not need to index them. I've not used it much, but I have used it for transitions, and they definitely indexed the issues, so I suspect there's something else going wrong. Does the log have any errors when issues have automated events happen?