...
1 | Key | Project Key | Issue Type | Summary | Issue Links | Requirement Path |
|---|---|---|---|---|---|---|
2 | SC | Functional Requirement | New functional requirement | specified by:3 | SandCastle Project/Component Requirements | |
3 | SC | System Requirement | New system requirement | specifies:2 | SandCastle Project/System Requirements | |
4 |
| SC | Test Case | New test case | tests:SC-10 | SandCastle Project/Test Cases |
Create
...
The Requirement Path field is used to create parent-child relationships. The path of the child issue is that of the parent issue, plus the issue key of the parent. For example, if the parent path is “Sand Castle Project/Component Requirements” and the key of the intended parent is “SC-20”, then the path of the child is specified as “Sand Castle Project/Component Requirements/SC-20”. This method also works for new children.
The parent item must already exist in Jira.
The following example shows how the existing issue SC-21 is added as a child of SC-20 and how a new issue is added as child of SC-21:
...
Key
...
Project Key
...
Issue Type
...
Summary
...
Requirement Path
...
SC-20
...
SC
...
Functional Requirement
...
Existing Functional Requirement of SandCastle (SC) project
...
Sand Castle Project/Component Requirements
...
SC-21
...
SC
...
Functional Requirement
...
Existing requirement, add as child requirement to SC-20
...
Sand Castle Project/Component Requirements/SC-20
...
SC
...
Functional Requirement
...
New requirement, add as child requirement for SC-21 (nested)
...
Sand Castle Project/Component Requirements/SC-21
Create new predefined field values
...