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

Backlog: when a feature is updated on the Feature Backlog, it disappears from it until the page is refreshed

XMLWordPrintable

    • 12
    • Severity 3 - Minor
    • No

      Issue Summary

      When using the Feature Backlog, if one Feature is opened and updated, after saving/closing, it will disappear from it, and will only re-appear if the page is refreshed. Other Backlogs (like Epics/Stories) don't have the same problem.
      See one example:
      The feature can be seen on the backlog:


      After saving the update, it disappears:


      And only after the refresh of the page it appears once again:

      Steps to Reproduce

      1. Go to the Feature Backlog
      2. Select a Portfolio/Program + PI
      3. Open one Feature and update it, save/close
      4. See how the Feature is not present anymore
      5. Now refresh the page and see how it re-appear

      Expected Results

      After saving a Feature, it would be visible on the backlog without the need for a refresh of the page.

      Actual Results

      A refresh is needed to make the Feature appear on the backlog

      Workaround

      A refresh is needed to make the Feature appear on the backlog

        1. backlog_5.png
          backlog_5.png
          391 kB
        2. backlog_1.png
          backlog_1.png
          392 kB
        3. backlog_3.png
          backlog_3.png
          379 kB
        4. backlog_4.png
          backlog_4.png
          395 kB
        5. backlog_2.png
          backlog_2.png
          476 kB
        6. alignsupport.jiraalign.com.har
          2.22 MB

            [JIRAALIGN-4414] Backlog: when a feature is updated on the Feature Backlog, it disappears from it until the page is refreshed

            Kyle Foreman added a comment -

            Hello,

            This issue is fixed in the version noted above.

            -The Jira Align team

            Kyle Foreman added a comment - Hello, This issue is fixed in the version noted above. -The Jira Align team

            Anna Eshlin De Kassal (Inactive) added a comment -

            The issue had been fixed in 10.116.0

            Anna Eshlin De Kassal (Inactive) added a comment - The issue had been fixed in 10.116.0

            Sonja Peterson added a comment -

            This is causing a lot of confusion and upset in meetings for us when features disappear and having to refresh every time to select the value stream view, again and again, is not really the best experience. Please prioritize this fix. 

            Sonja Peterson added a comment - This is causing a lot of confusion and upset in meetings for us when features disappear and having to refresh every time to select the value stream view, again and again, is not really the best experience. Please prioritize this fix. 

            Rodrigo Alvarez added a comment -

            this is so prominent and frequently used that deserves attention

            Rodrigo Alvarez added a comment - this is so prominent and frequently used that deserves attention

            Sarah.Green added a comment -

            Our teams spend a lot of time in the Feature Backlog, so speedy resolution of this issue would be so appreciated! 

            Sarah.Green added a comment - Our teams spend a lot of time in the Feature Backlog, so speedy resolution of this issue would be so appreciated! 

            Ratna Lekkala added a comment - - edited

            This issue is getting lot of traction form our users. Can we please expedite the solution for this issue in the nearest release possible?

            Ratna Lekkala added a comment - - edited This issue is getting lot of traction form our users. Can we please expedite the solution for this issue in the nearest release possible?

              dfuller@atlassian.com Don Fuller
              a8cff3407f0b Diego Larangeira
              Affected customers:
              10 This affects my team
              Watchers:
              28 Start watching this issue

                Created:
                Updated:
                Resolved: