Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-4241

Issues with no workflow actions after upgrade

XMLWordPrintable

      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.

            [JRASERVER-4241] Issues with no workflow actions after upgrade

            Conny Postma made changes -
            Remote Link Original: This issue links to "Page (Atlassian Documentation)" [ 77368 ]

            Richard Cross added a comment -

            tl;dr:

            Richard Cross added a comment - tl;dr: Integrity Checker doesn't scale to large Jira instances, and Atlassian have no plans to fix it: https://jira.atlassian.com/browse/JRASERVER-17593 Instead, we need to run SQL alternatives to fix Issue/Workflow/DB inconsistencies: https://confluence.atlassian.com/jirakb/sql-equivalents-for-jira-server-s-workflow-integrity-checks-658179102.html
            Olga Springer made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 746725 ]
            Antoni Kowalski made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 746492 ]

            Nikita Subbotin added a comment -

            Same issue on 8.20

            Integrity check takes YEARS to complete, not the best solution.

            Nikita Subbotin added a comment - Same issue on 8.20 Integrity check takes YEARS to complete, not the best solution.

            Christian Pascher added a comment - - edited

            we could reproduce the issue with the following steps:

            1. somebody opens the create issue screen on a new page (link: https://<instance>/secure/CreateIssue!default.jspa)
            2. fill out the fields you want
            3. click multiple times on "Create" before the page reloads/changes

            the created issues are than broken on a 8.13.10 DC

            is also described here JRASERVER-37267

            Christian Pascher added a comment - - edited we could reproduce the issue with the following steps: somebody opens the create issue screen on a new page (link: https://<instance>/secure/CreateIssue!default.jspa) fill out the fields you want click multiple times on "Create" before the page reloads/changes the created issues are than broken on a 8.13.10 DC is also described here  JRASERVER-37267

            Richard Cross added a comment - - edited

            Experiencing this in 8.15.0

            It affects issues that have merely been created, and not yet transitioned; it would be lovely to know what's causing this at the very least.

            Like everyone else, running the integrity checked finds and fixes the problem, but it's very slow and inconvenient.  If Atlassian can't fix this, perhaps they should provide a REST API call that automatically fixes whatever the Integrity Checker deems broken?

             

            Richard Cross added a comment - - edited Experiencing this in 8.15.0 It affects issues that have merely been created, and not yet transitioned; it would be lovely to know what's causing this at the very least. Like everyone else, running the integrity checked finds and fixes the problem, but it's very slow and inconvenient.  If Atlassian can't fix this, perhaps they should provide a REST API call that automatically fixes whatever the Integrity Checker deems broken?  

            Dwain Mathis added a comment -

            We are also experiencing this issue after an upgrade to 8.17.1.

             

            Running the integrity checker and fix corrected the problem.

            Dwain Mathis added a comment - We are also experiencing this issue after an upgrade to 8.17.1.   Running the integrity checker and fix corrected the problem.

            Loredana Aiello added a comment -

            We are also hitting this same issue in 8.13.5

            The workaround : running integrity checker and fix

            Loredana Aiello added a comment - We are also hitting this same issue in 8.13.5 The workaround : running integrity checker and fix

            Scott Torbert added a comment -

            We are also hitting this same issue in 8.11.1

            The workaround to move Jira to another Jira type and back worked

            Also running integrity checker and fix

            Scott Torbert added a comment - We are also hitting this same issue in 8.11.1 The workaround to move Jira to another Jira type and back worked Also running integrity checker and fix

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Affected customers:
              1 This affects my team
              Watchers:
              98 Start watching this issue

                Created:
                Updated:
                Resolved: