Identifying Issues in the Same Hierarchy
On the Profile Admin page, assume the following:
In the Issue Tree Open Statuses field, a comma-delimited list of status values is specified that indicate an Open status with the primary issue tracking system.
In the Issue Tree Closed Statuses field, a comma-delimited list of status values is specified that represent a Closed status.
There is a special field in an issue tracking system to hold a Parent Id that is the Id of its parent issue.
In the Create Approval Request page when an issue Id is entered, REST API connected to SAM will use the Parent Id field and find all issues in the primary issue tracking system that are in the same hierarchy and have one of the statuses defined in the Issue Tree Open Statuses field. These issues are further filtered in SAM.
For example, assume that there are six issues identified as shown in the following table. If the Issue Tree Open Statuses is set to Open, Awaiting review, in the Create Request page when the issue Id 2 is entered, then REST API connected to SAM would find all issues in that hierarchy:
| Issue Id | Parent Id | Status |
|---|---|---|
1 |
2 |
Open |
2 |
3 |
Open |
3 |
Not applicable |
Closed |
4 |
3 |
Awaiting review |
5 |
6 |
Open |
6 |
Not applicable |
Open |
It would find issue 1 because 1 is a child of 2
It would find issue 3 because 3 is the parent of 2
It would find issue 4 because 4 shares the same parent as 2
It would not find issues 5 or 6 since they are not related at all to 2
So 1, 2, 3 and 4 are found by REST API. However only 1, 2 and 4 have a status value listed in Issue Tree Open Statuses, so 3 is ignored. Hence, REST API connected to SAM finds issues from 1 to 4, SAM filters out issue 3 and SAM shows issues 1, 2, and 4. For more information, see REST APIs for SAM.