-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
6
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Steps to reproduce:
- Create a project and edit its workflow.
- On any of the status, add a workflow properties jira.issue.editable with value false
- Publish the workflow.
- Create an issue and transition it to the status with the workflow properties above.
- After the targeted status is set to the issue, run the following REST api.
curl -X GET <JIRA Base URL>/rest/api/latest/issue/<Above issue key>/editmeta -u <username>:<password>
Expected Result:
- As in the previous response, it will show the fields that could be edited.
- Returns message that the issue is not editable.
Actual Result:
- This returns instead:
{"fields":{}}
Notes:
If the actual results is actually what is expected, it would be great if it returns a message that it is not editable instead.
- is related to
-
JRASERVER-66202 Document why REST editmeta requires Issue Key/ID
- Gathering Interest
- relates to
-
JRACLOUD-63664 Get edit issue meta REST call returns empty fields for non editable issue.
- Closed