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

Debugging workflow transitions

Jason Vou1

Hi everyone, please pardon any ambiguities or confusion since this is my first post and I am new to being a JIRA admin. I've created a custom workflow and attached it to a scheme that a project is referencing. When I go and create an Issue Type (in this example, a 'story' issue type) and try to start the workflow, I am getting an error with the following message:

The start of my workflow is here:

I get the exception when on the "Not Started" state trying to click "Start Development" to transition to the "Dev Started" state.

Any help would be greatly appreciated! Thanks!

Accepted answers

All comments

Norman Abramovitz

We would need the transition definitions and post functions to understand what is breaking.

Jason Vou1

Not Started (1)	Not Started	Start Development (11) >> Dev Started	View Properties
Dev Started (2)	Dev Started	Stop Development (21) >> Not Started Complete Development (51) >> Dev Completed Blocked (131) >> BLOCKED Suspend (451) >> Suspended	View Properties

Workflow Browser

Not Started

Start Development (11)

Dev Started

(Originating Steps)

(Destination Step)

Post functions:

Set issue status to the linked status of the destination workflow step.

— THEN

Add a comment to an issue if one is entered during a transition.

— THEN

Update change history for an issue and store the issue in the database.

— THEN

Re-index an issue to keep indexes in sync with the database.

— THEN

Fire a Generic Event event that can be processed by the listeners.

My apologies. Is this sufficient information? Please let me know if there is anything else. Again, I appreciate the help and quick response!

Jo-Anne MacLeod

Have you tried to rebuild your index to see if that is the problem?

Jason Vou1

Jo-Anne,

Thanks for the quick response. The only change I've made is changing the unit of tracking from minutes to hours. I am getting a message that states I should re-index but am curious as to how this could affect the workflow.

Thanks again for the help!

Jason Vou1

Hi,

I've just tried re-indexing (which took less than 10 seconds since we don't have many projects in JIRA) and am still receiving the original error. The re-indexing message is gone now.

Thanks.

Nic Brough -Adaptavist-

Ouch, that looks like a corrupted issue in the database. I see you've tried re-indexing, which is always worth a shot.

However, I'd run the integrity checker. This can correct entries in the database if they've been damaged.

If that helps, then it's worth thinking about the causes. In my experience, there are three main reasons

Someone or something did a hard kill on the server running Jira. Anything from a "kill -9" to feeding the server coffee (don't laugh, I had a cat tip a mug down the back of my machine once. Can't blame anyone other than the idiot who left the coffee there though - me)
Bad code - plugins can make a mess of the database, but they have to try really hard via the API. I guess core code could do it too, but I suspect Atlassian would have ironed those out well before version 2...
Someone ran SQL against the database while Jira was running. (Find them and remove their access - you should never allow this. Reading is fine, but not write)

Jason Vou1

Hi Nic,

Thanks for the advice. I ran the integrity checker and everything passed successfully. I'll continue debugging with those reasons in mind. If you have any other ideas of how to debug this or where I can look, I would greatly appreciate it.

Thanks for your help!

Jo-Anne MacLeod

Are you in a position where you can do a restore to yesterday's backup? Probably in a test environemnt. Just to see if it corrects the problem. You may lose a days work, but it is better than not being able to move forward.

Jason Vou1

Jo-Anne - I personally am not but will check with other members of the team to see if this is possible. Thanks for the suggestion.

Also, just to supplement my previous comment, here are the results of the Integrity Checker tool.

Welcome!

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

Quick Links

Find more posts tagged with

jira

workflow

exception