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

Jira Management Yellow Warning Message doesn't show the real error root cause


    • 1
    • Severity 2 - Major
    • No

      Issue Summary

      A customer with the following scenario: 3 Jira Projects feeding 1 Jira board connected to align,  sees the yellow warning message in Administration > Jira Management > Boards.
      The Warning message says :No Jira project was found. Verify that the connector service account has permission to view the board and that the board has a filter share with the project. 
      However all the Jira shares and permission are setup correctly, and using the Splunk i was able to find out the real error root cause that better describes what is happening: 

      Level: Warning
       MessageTemplate: Board Decepticons (1939) has multiple Jira Projects associated with it.
      Unknown macro: \{ [-] Action}
      RenderedMessage: Board Decepticons (1939) has multiple Jira Projects associated with it.

      CONCLUSION: The way i see this message in the block above should be shown in the UI for the customer, since it matches with the correct situation.

      Steps to Reproduce

      1. Jira Side creates 3 projects
      2. Assign and give the properly permission for this 3 projects to only one board
      3. On Jira Align Administration > Jira Setting > Configure 1 project at least to be connected to align 
      4. Side Administration > Jira Management > Boards configure the board to be manageable by align
      5. Detect the yellow Warning message still fixed for this board
      6. Looking into Splunk logs you can see the the real root case by searching for :has multiple Jira Projects associated with it.

      Expected Results

      My expectation would be the Yellow Warning message showing up also this sentence: 

      "Board XXXXXX (XXXXX) has multiple Jira Projects associated with it."

      Actual Results

      This Yellow warning message is showing the wrong root cause description:



      No workAround

            kforeman@atlassian.com Kyle Foreman
            f58471712ff6 Victor Fragoso
            1 Vote for this issue
            4 Start watching this issue