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

[JIRAALIGN-1223] Dependency: Cross Program/PI Kanban to Agile team dependency should show up on the program board for the responding team

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: High High
    • 10.75
    • 10.65
    • program - dependencies
    • None
    • 1
    • Severity 3 - Minor
    • Batman! - SCORP6

      Issue Summary

      There is a problem, when cross-program and cross-pi dependency doesn't show up on the responding team program board, grid, team room, etc.

      Steps to Reproduce

      1. There should be 2 teams. Team1 should be of the type 'Kanban' and should live within its own hierarchy - protfolio1, program1, PI1. Team2 should be of the type 'Agile' and should exist within another hierarchy - portfolio2, program2, PI2, should have sprints generated from the anchor dates, sprints should fit into the release start and end dates.
      2. Both teams should contain team members whose roles are not super admins, team lead roles are ok.
      3. As a super admin create team dependency where kanban team1 is requesting team and agile team2 is a respondent.
      4. Commit to the dependency, committed sprint should be within responding team PI dates.
      5. Impersonate team member from team2
      6. Set the program2 and PI2 into the context menu and open the dependency grid or program board

      Expected Results

      The dependency should be displayed in all respective places for the responding team - program board, team room, grid, etc.

      Actual Results

      The work item doesn't show up for the responding team in neither of the places

      Workaround

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

            cgottlieb@atlassian.com Caz (Inactive)
            vvyhovskyi@atlassian.com Vitalii Vyhovskyi
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated:
              Resolved: