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

[JIRAALIGN-2776] API 2.0: defectAllocation is set to "1" when creating Sprints via POST call towards /align/api/2/Iterations endpoint

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Low
    • 10.91
    • 10.86, 10.87
    • REST API
    • None
    • Severity 3 - Minor
    • Breakers - VH4
    • No

    Description

      Issue Summary

      When creating Sprints via POST call towards /align/api/2/Iterations endpoint, defectAllocation is set to "1", as opposed to UI behavior where defectAllocation is set to "0".

      UI-created Sprint API-created Sprint 
      "defectAllocation": 0
      		 
      "defectAllocation": 1

      Steps to Reproduce

      1. Browse to Sprints grid
      2. Create a new Sprint
      3. Via API, create a new Sprint using the same information used in the previously created record
      4. Make a GET call towards each of these records
      5. Compare both results

      Expected Results

      "defectAllocation" is pulled from the Anchor Sprint if this field is not provided by user manually.
      User should be able to set manually "defectAllocation" on creation/updating.

      Actual Results

      • API-created record comes with a value of "1"

      Workaround

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

      Attachments

        Activity

          People

            tdavenport@atlassian.com Tony D.
            rcortez@atlassian.com Rodrigo Cortez
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Backbone Issue Sync