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

Status not transitioned but history shows it did.

AnupamS

Hi Community,

We are seeing a very weird issue where few issues are showing to exist in an old status but in history it shows that they have been transitioned. There is no reverse transition to showcase if there is any undo. Same goes with resolution as well.

The transition is done through a custom plugin and the transition logic is correct where the plugin tries to change the issue status and resolution, but in the UI, it stays same. As far as I know, the history is written through the post function (which means issue status did go at-least till that point), but how it came back or why it didn't reflect in UI is a mystery. We are using 7.13.x (soon to be upgraded).

Can I get some insights on this?

Thanks

Accepted answers

Nic Brough -Adaptavist-

It sounds like your custom plugin is not actually doing a transition correctly, but still managing to trigger a history update. Or it's doing the transition, getting to the point of history write and then failing the rest.

How exactly does the custom plugin perform the transition?

All comments

Fazila Ashraf

@AnupamS , Could you try running the integrity checker?

May be the db has inconsistent information about that transaction.

AnupamS

Hi Fazila,

Nope, nothing on the integrity checker. That was the first thing I did when this issue came up.

Fazila Ashraf

Did you also do a reindex ?

AnupamS

Yes, instance was reindexed previously but I also indexed issues.

Nic Brough -Adaptavist-

How exactly does the custom plugin perform the transition?

AnupamS

Hi Nic,

Thank you for your response. We are using issueManager.updateIssue(....) for updating the issue.

The plugin uses the Jira APIs to do the transition, so I am not sure if really controls the Jira in-built threads once the relevant Jira APIs are triggered with the right params.

Also to add to the weirdness, the plugin handles thousands of issues and has been there for quite some days now. This is something we have observed very recently (hope the volume is not huge). So it's hard to zero down as majority of the issues we see are just fine, and the one with exceptions are not having anything significant that raises concern.

The post functions are the default ones and one additional scripted pf in the end that is harmless (at-least not fatal to undo the action)

Nic Brough -Adaptavist-

How exactly are you using issueManager.UpdateIssue? How are you feeding it the transition to execute?

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