Details
-
Bug
-
Resolution: Fixed
-
Medium
-
None
-
3.0 Professional Beta, 3.0 Enterprise Beta, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.1, 3.1.1
-
3
-
Description
Occasionally people report that JIRA issues have no workflow. A SQL query like:
select jiraissue.pkey, jiraissue.workflow_id, OS_WFENTRY.* from jiraissue, OS_WFENTRY where jiraissue.workflow_id=OS_WFENTRY.id and ( OS_WFENTRY.STATE is null or OS_WFENTRY.STATE = 0);
shows workflows whose STATE column contains null or 0 values, where they should be 1:
+---------+-------------+-------+------+-------------+-------+ | pkey | workflow_id | ID | NAME | INITIALIZED | STATE | +---------+-------------+-------+------+-------------+-------+ | FOO-45 | 13679 | 13679 | jira | NULL | 0 | | FOO-46 | 13680 | 13680 | jira | NULL | 0 |
It seems we have a bug somewhere, perhaps an upgrade task for 2.6 is not completing, but marking itself as completed.
Anyway, we should write an integrity check to detect and fix this.
Attachments
Issue Links
- has a regression in
-
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
(1 mentioned in)
