Create links between new issues or between new and existing issues
Links between new Jira issues are created by using the Excel row numbers of the issues in the Issue Links column. To create links between new Jira issues and existing issues, you use the issue key of the existing issue instead of a row number. (If the existing issue is also in the worksheet, you can use either the row number or the issue key.) The following example shows how to create links of type “specified by” and “specifies” between two new issues and to create a link of type “test” between a third new issue and an existing issue. It is not required to define both ends of the relation, Jira will take care for the second part:
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 parent-child relationships
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
Fields such as Fix Versions contain values that are predefined by users with the appropriate project permission, e.g. the project administrators. If you have the permission to create the predefined values of a given field, and you enter a new value for the field in Excel, it will be added as a new predefined value to the project. If you do not have the project permission, the update is refused and reported as an error in the results summary.
Add values to multi-selection fields
Multiple values can be created in fields such as Labels by placing the values on new lines. The following example shows how to do this for the fields Labels, Issue Links and Fix Versions:
Key | Project Key | Issue Type | Summary | Labels | Issue Links | Fix Versions |
|---|---|---|---|---|---|---|
SC-25 | SC | Functional Requirement | Add Labels and Versions | important | trace to:SC-15 | 1.0 |
Create comments
New comments can be created by entering a value in the column Comments.
Sub-task creation and linking
Overview
The plugin supports sub-task load, upload and creation. User can add sub-tasks to a new or existing parent issues using a new field "Sub-task Parent key".
Instructions to create and link Sub-task
Load the Jira project in excel with field type “Sub-Task Parent Key”
Add a new issue in excel with Issue type “Sub-task”
Update the “Sub-Task Parent Key” for this issue
Upload the changes
The Sub-task will be created on Jira and linked to the parent issue
Additional line reference feature:
The "Sub-taks Parent Key" also understands when the number of a line in excel is updated instead of an Issue Key. If you want the parent of the Subtaks to be the issue on line 4, then write "4" into the "Sub-taks Parent Key".
Limitations:
Changing the parent of a Sub-task is a feature only available through the Jira webpage, trying to do so through the plugin is not possible at the moment.