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

[JIRAALIGN-2775] API 2.0: Sprint Members are not populated when creating Sprints via POST call towards /align/api/2/Iterations endpoint

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 10.97.0
    • 10.87
    • REST API
    • 1
    • Severity 3 - Minor
    • Breakers - WT1
    • No

    Description

      Issue Summary

      When creating Sprints via POST call towards /align/api/2/Iterations endpoint, Sprint Members are not getting populated, as opposed to UI behavior.

      Members tab of an
      UI-created Sprint
      Members tab of an
      API-created Sprint
      • Same ReleaseID, ProgramID and TeamID were used

      Steps to Reproduce

      1. Browse to Sprints grid
      2. Create a new Sprint
      3. Notice members in the Members tab are populated
      4. Via API, create a new Sprint using the same information used in the previously created record
      5. Run a GET call or browse the Sprints grid for the newly created record
      6. Notice the Members tab is empty

      Expected Results

      • Both UI- and API-created records should behave identically

      Actual Results

      • API-created record is missing the member relationship

      Workaround

      • Manually relate members in the UI

      Attachments

        Issue Links

          Activity

            People

              ronyshchuk@atlassian.com Roman
              fd18f17e9ccb align-connector-bot
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync