Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Generally all System fields and Custom field types are supported. For some there is a special handling provided to match with the editing capabilities of Excel. Field types of 3rd-party apps may be supported depend on the implementation strategy of the app vendor.

Table of Contents
minLevel1
maxLevel7

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
severe

trace to:SC-15
trace from:SC-21

1.0
2.0

Linked Issues

With the field “Issue Links” you can maintain the link relation and the connected Jira issue key.
When you add in Excel only one side of the relation, Jira will automatically update the other issues link.

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 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
severe

...

trace to:SC-15
trace from:SC-21

...

1.0
2.0

Comments

Comments of Jira issues listed as Excel comments. They can not be updated. Number of latest comments can be configured in the settings dialog.

Create comments

New comments can be created by entering a value in the column Comments.

Sub

...

-Task

The relation between a sub-task (Jira issue type) and a parent can be retrieved by the field “Sub-Task Parent Key”.

Creation and linking of Sub-Tasks

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

...

  • your sub-task issue type, e.g. “Sub-task” (or similar, depend on your Jira coniguration)

  • 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-

...

task Parent Key" also

...

accepts also the

...

Excle line number instead of an Issue Key. If you want the parent of the

...

sub-task to be the issue on line 4, then write "4" into the "Sub-

...

Task 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.

  • Creation of sub task (issue type) without a parent is not allowed by Jira.