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

Team Dependency Map: Sprint/Date field shows 'NONE' as a value in the REQUESTED column

    XMLWordPrintable

Details

    • 1
    • Severity 2 - Major
    • No

    Description

      Issue Summary

      In the "Team Dependency Map" page, Sprint/Date field shows the 'NONE' as a value (instead of the actual Needed By/Committed By date) in the REQUESTED column.
      This behavior only happens when the Dependency's "Requesting Team" is a Kanban type. ( It doesn't matter the type of the "Depends on" team.)

      Steps to Reproduce

      1. Login to Jira Align
      2. Set the T1 filters: select Portfolio and PI
      3. Go to the Dependencies grid
      4. Create a Dependency ( Fill the fields PI/Release, Feature, Depends On, Needed By, Committed By ) + ( For the "Requesting" field, select one Kanban Type team )
      5. Go to the "Team Dependency Map" page. Select Team ( the same team that we used as a Requesting Team in the previous step ) and the PI
      6. Look at the "Ranked Dependency List For" section for that 'Requesting Team'

      Expected Results

      In the 'REQUESTED' column, the Sprint/Date field shows the real date value of ( Needed By / Committed By)

      Actual Results

      In the 'REQUESTED' column, the Sprint/Date field shows 'NONE' as a value

      Workaround

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

      Attachments

        1. Screenshot 2022-09-08 at 12.01.04.png
          484 kB
          Niyazi Fellahoglu
        2. Screenshot 2022-09-08 at 12.01.28.png
          796 kB
          Niyazi Fellahoglu

        Issue Links

          Activity

            People

              dfuller@atlassian.com Don Fuller
              2d9e3a4549ac Niyazi Fellahoglu
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync