Issue Summary

This is reproducible on Data Center: no, though regularly affecting customers

Steps to Reproduce

1. Create an Issue during some excessive load in Jira, like Full GCs, DB connection overload, etc
2. Observe the Issue will lack the Status transition buttons

This has also been observed when the Issue's created but unable to be reindexed (like JRASERVER-74514).

Expected Results

1. The Issue would either fail to be created or be sucessfully created and have the Status transition buttons available

Is it possible to have the os_wfentry.state be initialized with 1 instead of 0?

Actual Results

1. The Issue's created (possibly not indexed) and is missing the Status transition buttons

The Issue's first created with a os_wfentry.state of 0, then it's updated to 1. This happens outside a DB transaction, so an interruption may lead to the os_wfentry record being left in an invalid state = 0.

Workaround

Wither run the Database Integrity Checker or manually update the Issues with state = 0 to state = 1 on the os_wfentry table, as described in:

• Workflow transition button missing from the issue view page in Jira server

 
This is impacting customers in a way they have to deal with this right after dealing with the initial degradation or outage that causes the Issues to be created in an invalid state.

This also impacts end-users directly and being unable to transition Issues tends to escalate quickly across their companies.