Issue Summary

'Process Step' info in the API JSON file refers to unknown Id's

Steps to Reproduce

1. Create a JSON file for creating/updating an Epic or Feature. For the Process Step, you have to enter an Id in one of the fields developmentalStepId, operationalStepId, additionalDevelopmentalStepIds, additionalOperationalStepIds. These Ids are unknown to the user.

2. Expected Results
The user should be able to enter Process Step names, OR, there should be a REST API call that retrieves the IDs together with the names.

3. Actual Results
The user does not know what id's to fill in

Expected Results

The user should be able to enter Process Step names, OR, there should be a REST API call that retrieves the IDs together with the names.

Actual Results

The user does not know what id's to fill in

Workaround

The "suggested" workaround is to first do a GET of an Epic and Feature, look at the Process Step value in the GUI, compare it with the process step ID returned in the GET operation. However, this does not work in the case of automation. First of all, this is manual work, that has to be done for all process step values, and by all users that want to use the REST API. And has to be redone after every change of the process steps.

But the obtained values are also different in the production environment and the staging environment, so you have to keep copies of scripts for each environment. This may cause testing completely useless (you test other scripts than the production scripts).

More, this is NOT only about process step IDs. In fact, all data in the REST API is ID-only based. What makes it is impossible to use in an automation environment (other than just doing some simple ad-hoc REST queries). You need to do manual bookkeeping of all the ID-name relations of the objects in the environment. And this bookkeeping is different in the different environments.