| Info |
|---|
First you need to import some issues to get the metadata from projects. Then use the Export button to send changes in imported issues to your Jira instance. Also you can create new Jira issues (using Create button), it will create a new row for issue. Creating new issue can be initialized also by '#' sign. |
Excel 365 Connector allows you edit Jira issues in Excel then export (send) those changes back to Jira.
In this section we will cover topics like preparing new/edited issues for export and finally sending changes.
| Table of Contents | ||||
|---|---|---|---|---|
|
After https://psc-software.atlassian.net/wiki/spaces/EC365/pages/2411986945 you can edit all the issues you are interested in (1) by moving the cursor to the row with the issue and editing the column associated with the Jira Issue field.
Jira permissions and restrictions apply, eg. if you cannot change priority in Jira → you won't be able to send those changes to Jira
Editing imported issue
When you look at the sheet with fetched issues you will see cells with white and grey background color.
To make changes to issues to just click on the cell. in the row of the issue which you want to change the value for that cell, eg. change summary, or assignee.
When you start editing cell those colors will change:
Yellow - values in these fields can be edited
Orange - you have already edited in Excel (e.g. change in issue type or description)
Grey - fields that cannot be edited (it might be related to issue permission or other Jira restrictions)
Creating new issue
| Note |
|---|
You need to import some issues to get the metadata from projects. |
Create button
To add a new issue just click Create (1) button, it will create new row in the spreadsheet starting with '#' in the Key column.
Now you need to fill fields with dark green color (2) - those are required fields. Moreover, when you choose project and issue type → metadata will be checked and required fields for this combination will be marked with dark green also.
Light green (3) color will mark other (optional) fields available for edition eg. Description, Assignee, Priority, Fix Version.
| Info |
|---|
Should you fill all of the fields? It’s up to you, your project requirements and your Jira configuration. |
Use '#' sign
You can also create new issue, just by typing '#' in the key column, it works just the same as the create button, but it can speed up the process for creation of multiple new issues
| Info |
|---|
Eg. #-1 in the column field can be used as temporary issue ID, and can be used to create issue structures like Parent + Subtasks: Export issue structures |
Exporting data
When you are ready either with editing existing data or creating new issues (1), just click Export (2) button.
A pop up window will appear with information about changed and new issues
You will be informed about the number of new and edited Issues (1). When you click Export (2), the data will be sent to your Jira instance. If all goes well you will notice changes in colors.
| Info |
|---|
If some of the cells become red (while editing or sending changes), this indicates that the data you entered does not exist or is incorrect according to the Jira instance (or permissions). You will receive a warning/error with information about what is wrong with your data. |
| Tip |
|---|
Temporary IDs starting with '#' changed into Jira issue keys. You can cling on it to check it on Jira |
Limitations
In case of performing actions limited by license, appropriate message will be displayed.
Exporting data - Evaluation License
Some actions are limited or restricted in the evaluation license, those are related to operations performed on large sets of data or creating issues structures. In needed contact your Jira administrator to verify if there is valid license applied in Jira.
Exporting data - Insufficient License
In case of the wrong license eg. expired or missing licence, you will see appropriate message, then please contact your Jira administrator to verify if there is valid license applied in Jira.
