When user specifies a non-existent Person ID, REST Api should return a 400 error

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 8.0.0, 8.22.6, 9.0.0, 9.4.10, 9.11.0
    • 8
    • 4
    • Severity 3 - Minor
    • 0

      Issue Summary

      This is reproducible on Data Center: (yes) 

      When making a REST call and the Person ID is specified, the Person is created which leads to confusion that this endpoint can assign an existing Person with a team. 400 error code should be returned instead. 

      Steps to Reproduce

      1. Make a call to
      POST {{base_url}}/rest/teams-api/latest/resource
      Body:
      {
        "teamId": 8,
        "person": {
            "id": 123
            "jiraUser": {
            "jiraUserId": "any existing user"
          }
        }
      } 
      

      Expected Results

      400 HTTP error code

      Actual Results

      Persona is created and ID is not taken into account.

      Workaround

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

            Assignee:
            Unassigned
            Reporter:
            Stasiu
            Votes:
            1 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: