-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
Issue Summary
Atlassian has completely deprecated the use of usernames from its REST API. Whenever admins try to create or update an issue using username, the application will show a misleading message about the field being required, instead of informing the wrong format of the input.
This is misleading in environments where that field is not required, as omitting the information successfully creates or updates the relevant issue.
Steps to Reproduce
- Post a request to rest/api/2/issue;
- use username on the reporter field, as example.
Expected Results
The following message is shown: "Usernames has been completely deprecated from the REST API. Please leverage the Atlassian Account ID for the relevant user".
Actual Results
The following message is shown: "Reporter is required".
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team