Uploaded image for project: 'Jira Align'
  1. Jira Align
  2. JIRAALIGN-6742

Inconsistent behavior while updating Process Steps for Epics in Different browsers

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 10.132.3
    • 10.120.0, 10.130.3
    • Epics - Action
    • 2
    • Severity 3 - Minor
    • No

      Issue Summary

      When updating Process steps for Epics with multiple browsers, the Process State will not reflect the change made in the other browsers.

      I recorded a gif to make it clear.

      This is reproducible on Data Center: yes

      Steps to Reproduce

      1. Open an Epic in Jira Align that has two levels of Process step setup using Chrome browser.
      2. Open the same Epic in Jira Align using Edge browser.
      3. Update the second level of the Process Step in Chrome, save it.
      4. Go to Edge, refresh the page, at first it will reflect the changes, now update the same field and save.
      5. Go to Chrome, refresh the page, it will not reflect the new update. Now update the same field and save again.
      6. Go to Edge, refresh the page, it will not reflect the change made.

      The data will be updated in the database though.

      Additional information:

      • The issue is persistent in new UI and old UI.
      • The issue does not change if “Map State to Process Step” is turned on/off, for both or either process flow.
      • The updates in the Process Step are not being recorded in the Audit log of the Epic.

      Expected Results

      The data to be consistently updated using different browsers as many times the Process Step field is updated.

      Actual Results

      Inconsistent behavior when saving the Process step field between multiple browsers.

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            5ed8ef87d2cd Karen Bradshaw
            121fc1e6b3d8 Andre Deme
            Votes:
            3 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: