-
Suggestion
-
Resolution: Fixed
-
None
You need to account for the case where the jiraissue.issuestatus is null.
We had quite a large number of these - and in all cases, the worflow status was ok - so it was just a matter of updating jiraissue with the value from OS_WFENTRY
REPORT:
SELECT jiraissue.pkey, OS_WFENTRY.STATE, jiraissue.issuestatus FROM jiraissue INNER JOIN OS_WFENTRY ON jiraissue.WORKFLOW_ID = OS_WFENTRY.ID WHERE (jiraissue.issuestatus IS NULL) ORDER BY jiraissue.pkey;
FIX:
update jiraissue set issuestatus = ( select state from os_wfentry where id = workflow_id ) where issuestatus is null;
And pls make it efficient (no N+1 database calls...) - the other integrity checks are quite slow because of inefficient database access...
[JRASERVER-7428] Workflow Integrity Check needs an additional check
Remote Link | Original: This issue links to "Page (Atlassian Documentation)" [ 77367 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 746726 ] |
Remote Link | New: This issue links to "Page (Confluence)" [ 746493 ] |
Workflow | Original: JAC Suggestion Workflow [ 3052041 ] | New: JAC Suggestion Workflow 3 [ 3678440 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2614831 ] | New: JAC Suggestion Workflow [ 3052041 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2579431 ] | New: Confluence Workflow - Public Facing v4 [ 2614831 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2358304 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2579431 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 2125700 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2358304 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2088185 ] | New: JIRA Bug Workflow w Kanban v6 [ 2125700 ] |
Workflow | Original: JIRA Bug Workflow w Kanban v6 [ 889362 ] | New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2088185 ] |