-
Bug
-
Resolution: Unresolved
-
Low
-
1
-
Minor
-
1
-
Issue Summary
When using the Bulk Get Workflows REST API
If the Workflow has not been edited then the startPointLayout and layout fields are not populated.
Steps to Reproduce
- Create a new Company Managed Project
- Make a REST call to /rest/api/3/workflow/search to get the entityId of the Workflow for the Project
curl --silent --user <email>:<token> --request GET \ --url 'https://<yoursite>.atlassian.net/rest/api/3/workflow/search' \ --header 'Accept: application/json'
- Make a call to get the details of the Workflow
curl --silent --user <email>:<token> --request POST \ --url 'https://<yoursite>.atlassian.net/rest/api/3/workflows' \ --header 'Content-type: application/json' \ --header 'Accept: application/json' \ --data-raw '{"workflowIds":["<entityId>"]}'
Expected Results
The output will have the startPointLayout and layout fields.
"startPointLayout": {
"x": 605,
"y": 17.39998779296876
},
...
"statuses": [
{
"statusReference": "10001",
"layout": {
"x": 580.1062498092651,
"y": 167.39998779296877
},
"properties": {},
"deprecated": false
},
{
"statusReference": "10000",
"layout": {
"x": 578.5616703033447,
"y": 67.39998779296876
},
"properties": {},
"deprecated": false
},
{
"statusReference": "3",
"layout": {
"x": 557.7937507629395,
"y": 117.39998779296876
},
"properties": {},
"deprecated": false
}
],
Actual Results
The output does not have startPointLayout and layout fields.
"statuses": [
{
"statusReference": "10000",
"properties": {},
"deprecated": false
},
{
"statusReference": "10001",
"properties": {},
"deprecated": false
},
{
"statusReference": "3",
"properties": {},
"deprecated": false
}
],
Workaround
Edit the Workflow and save the Draft.
- relates to
-
JRACLOUD-74270 As a Jira admin, I want to be able to publish drafts and activate inactive workflows to make changes via the REST API
- Gathering Interest