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

Backlog - Portfolio Changes Whenever a Different Backlog View is Selected

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.69
    • 10.58
    • multiple - backlog
    • None
    • 1
    • Severity 3 - Minor
    • Hide
      1) Customer has multiple portfolios defined in their teir 1 menu.
      2) They navigate to the backlog in Jira Align.
      3) Along the way, they switch their backlog views from Epic View to theme View, for example.
      4) When this happens, the portfolio in the dropdown menu on the backlog page itself changes, UNLESS the portfolio selected is the last one in the list. Please see the screenshots submitted from the customer.
      Show
      1) Customer has multiple portfolios defined in their teir 1 menu. 2) They navigate to the backlog in Jira Align. 3) Along the way, they switch their backlog views from Epic View to theme View, for example. 4) When this happens, the portfolio in the dropdown menu on the backlog page itself changes, UNLESS the portfolio selected is the last one in the list. Please see the screenshots submitted from the customer.
    • Hide
      the selected portfolio should not change every time they switch to different backlog views (Epic, Theme, etc)

      Show
      the selected portfolio should not change every time they switch to different backlog views (Epic, Theme, etc)
    • The portfolio in the dropdown menu on the backlog page itself changes whenever the work type is swtiched, UNLESS the portfolio selected is the last one in the list.
    • Breakers - RHP9

      Issue Summary

      When the user changes the focus of their backlog to a different work (Epic, Capability, etc), it also changes the Portfolio, instead of staying with the portfolio originally selected. See the screen shot attached (img 001).

      The view before changing the work item, focus, with Infrastructure (img 002)

      This error is also seen when no PI is selected, unless the Portfolio is the last one in the drop down list.

      For example, switching from what is seend in img 003....

      To Themes there are no changes, because the selected Portfolio is the last one in the list. Please note the example in img 004 even though no PI is selected.

      If any other Portfolio selected selected, then it always changes it to the last value in the drop down list. (see img 005).

      The portfolio selections should not change every time a different work type is selected in the Backlog

      Steps to Reproduce

      1) Customer has multiple portfolios defined in their teir 1 menu.
      2) They navigate to the backlog in Jira Align.
      3) Along the way, they switch their backlog views from Epic View to theme View, for example.
      4) When this happens, the portfolio in the dropdown menu on the backlog page itself changes, UNLESS the portfolio selected is the last one in the list. Please see the screenshots submitted from the customer.

      Expected Results

      the selected portfolio should not change every time they switch to different backlog views (Epic, Theme, etc)

      Actual Results

      The portfolio in the dropdown menu on the backlog page itself changes whenever the work type is swtiched, UNLESS the portfolio selected is the last one in the list.

      Workaround

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

        1. image005.png
          image005.png
          25 kB
        2. image004.png
          image004.png
          18 kB
        3. image003.png
          image003.png
          18 kB
        4. image002.png
          image002.png
          13 kB
        5. image001.png
          image001.png
          53 kB

              idziadyk@atlassian.com Iryna Dziadyk (Inactive)
              kbaxley Kent Baxley
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: