Incorrect autoCompleteUrl for Assignee in createmeta REST API call

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 7.7.1
    • Component/s: REST API
    • None
    • 7.07
    • 1
    • Severity 3 - Minor
    • 0

      Summary

      Incorrect autoCompleteUrl for Assignee in createmeta REST API call

      Steps to Reproduce

      1. Run the following GET REST call in Jira: 
        "/rest/api/2/issue/createmeta?projectKeys= SSP&expand=projects.issuetypes.fields

        where SSP should be replaced by the Project Key

      Expected Results

      The autocomplete provides a rest call for the assignable users for that project:

      "assignee": {
"required": false,
"schema": {
"type": "user",
"system": "assignee"
},
"name": "Assignee",
"key": "assignee",
"autoCompleteUrl": "https://instance.net/rest/api/latest/user/assignable/search?project=SSP&query=",
"hasDefaultValue": false,
"operations": [
"set"
]
}

      Actual Results

      The Autocomplete URL is incorrect:

      "assignee": {
"required": false,
"schema": {
"type": "user",
"system": "assignee"
},
"name": "Assignee",
"autoCompleteUrl": "http://instance.com/rest/api/latest/user/assignable/search?issueKey=null&username=",
"hasDefaultValue": false,
"operations": [
"set"
]
}

      Notes

      This returns correctly in Jira Cloud.

      Workaround

      Use the REST call:

      GET /rest/api/2/user/assignable/search

      to find the assignable user for that project/issue. For more info: https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0/#api/2/user-findAssignableUsers

            Assignee:
            Unassigned
            Reporter:
            Mohamed Riza (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: