Missing Workflow and Issue
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
問題
This issue happens normally due to data corruption which is caused by connection issue to the database
The following appears in the atlassian-jira.log
2016-08-22 10:20:40,601 http-bio-8080-exec-10 ERROR xxx 680x628793x1 lptcgy xxx /secure/admin/workflows/ViewWorkflowSteps.jspa [web.util.component.RequestComponentManager] java.lang.IllegalStateException: No live workflow was found for 'xxx'.
java.lang.IllegalStateException: No live workflow was found for 'xxx'.
2016-08-22 10:52:11,311 http-bio-8080-exec-11 ERROR xxx 712x636959x2 d6cqok xxx /secure/admin/workflows/ListWorkflows.jspa [webwork.util.ValueStack] query="activeWorkflows/empty" {[id="activeWorkflows" type="8" values=""]} {[id="empty" type="8" values=""]}
java.lang.reflect.InvocationTargetException
診断
To verify if you are being affected by this problem, please perform the following SQL query in JIRA's database accordingly:
PostgreSQL and Oracle
SELECT id, workflow FROM workflowschemeentity WHERE workflow NOT IN (SELECT workflowname FROM jiraworkflows);
MS-SQL database
SELECT id, workflow FROM workflowschemeentity WHERE workflow collate SQL_Latin1_General_CP437_CS_AS NOT IN (SELECT workflowname FROM jiraworkflows);
MySQL データベース
SELECT id, workflow FROM workflowschemeentity WHERE BINARY workflow NOT IN (SELECT workflowname FROM jiraworkflows);
原因
This issue can happen if one or more workflow names stored in the workflowschemeentity
table do not match any workflow names stored in the jiraworkflows
table. One reason for this could be a Workflow Scheme that is associated with a deleted Workflow in the database, or there is an inconsistency in the characters' cases of the workflow name (e.g. "JIRA workflow" vs "JIRA Workflow").
The 'jira' workflow is a Read-only System Workflow so it is not in the 'jiraworkflows' table. If running the Diagnosis queries returns that workflow, then it is normal.
ソリューション
データベースの変更を行う場合は 必ず事前にバックアップを取得してください。可能な場合はテスト サーバーで変更を試すことをおすすめします。
Try to add the missing workflow from the logs again in JIRA. And retest. If does not work, proceed with below.
Jira をシャットダウンします。
After identifying the inconsistent workflow in the
workflowschemeentity
table, please update the entry/entries with the valid workflow name by running the following SQL update statement:UPDATE workflowschemeentity SET workflow = '<Correct Workflow Name>' where id=<ID of incorrectly named workflow>;
Remember to change the
Workflow Name
and ID to the correct value accordingly.(Oracle Only): Commit the transaction with the following:
COMMIT;
- After updating the related record(s) in the database, restart JIRA for the changes to take effect.