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

JIRA MANAGEMENT - Board points to wrong Jira Project if the Board's Project in Jira is moved to a new location and no Project is configured in the Board's Filter Share

XMLWordPrintable

    • 1
    • Severity 2 - Major
    • Hide
      1. On Jira, relocate a board to a new project location, however, do NOT add the new project location to the Filter Share in the Board's configuration settings. For example, only configure a Group in the filter share.
      2. While still in Jira, delete the old project that the board was associated with PRIOR to moving it.
      3. On Jira Align, navigate to Administration -> Jira Management and check the board.
      Show
      1. On Jira, relocate a board to a new project location, however, do NOT add the new project location to the Filter Share in the Board's configuration settings. For example, only configure a Group in the filter share. 2. While still in Jira, delete the old project that the board was associated with PRIOR to moving it. 3. On Jira Align, navigate to Administration -> Jira Management and check the board.
    • Hide
      Since the newly-relocated board was not associated with a project in the filter share, we should see a "No project found" on the Jira Management page.
      Show
      Since the newly-relocated board was not associated with a project in the filter share, we should see a "No project found" on the Jira Management page.
    • Hide
      The old, deleted Jira project still shows in Jira Align's Jira Management, even after deleting and re-adding the board. This was easily fixed by fixing the board's filter share on Jira to point to the correct project. However, if no project is configured in the filter share after the move, the Jira Management page should throw a "No project found" instead of pointing to the old one.
      Show
      The old, deleted Jira project still shows in Jira Align's Jira Management, even after deleting and re-adding the board. This was easily fixed by fixing the board's filter share on Jira to point to the correct project. However, if no project is configured in the filter share after the move, the Jira Management page should throw a "No project found" instead of pointing to the old one.
    • Stubborn Dragons - TART6

      Issue Summary

      If the location of a board in Jira is changed to point to a new project and the admin forgets to add the new project in the board's Filter Share settings, the Administration -> Jira Management page on Jira Align will still point to the board's old project instead indicating a "No Project Found" error.

      Steps to Reproduce

      1. On Jira, relocate a board to a new project location, however, do NOT add the new project location to the Filter Share in the Board's configuration settings. For example, only configure a Group in the filter share.
      2. While still in Jira, delete the old project that the board was associated with PRIOR to moving it.
      3. On Jira Align, navigate to Administration -> Jira Management and check the board.

      Expected Results

      Since the newly-relocated board was not associated with a project in the filter share, we should see a "No project found" on the Jira Management page.

      Actual Results

      The old, deleted Jira project still shows in Jira Align's Jira Management, even after deleting and re-adding the board. This was easily fixed by fixing the board's filter share on Jira to point to the correct project. However, if no project is configured in the filter share after the move, the Jira Management page should throw a "No project found" instead of pointing to the old one.

      Workaround

      For the affected board, log into Jira and make sure that the filter share is configured to point to the new project. This will fix the issue of the incorrect project being shown in Jira Align.

              ashaleev Anton Shaleev
              kbaxley Kent Baxley
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: