-
Suggestion
-
Resolution: Unresolved
-
None
-
191
-
108
-
Summary
Currently, it is not possible to create a new sprint when importing issues from CSV.
You can only map the issues to an existing sprint in your instance.
Suggestion
You can even select the map option when importing, but it expects a number (the id of the existing sprint):
Perhaps, there could be the possibility of sending a string so Jira could create a sprint using that string as the sprint's name.
Current workaround
As stated before, you can only map to an existing Sprint in your instance by parsing an id (corresponding to the sprint's id). So you need to create the desired sprint before the import.
1. Finding the id of a sprint:
- Perform an advanced search towards the Sprint field: Sprint = sprint:
- When the possible options are displayed (name of existing sprints), their id are displayed next to their name:
- Also, when selecting one of the sprints, their id will remains as the parameter for the search:
- When the possible options are displayed (name of existing sprints), their id are displayed next to their name:
2. Use the id corresponding to the desired sprint in your CSV file
- Example:
- Of course, you can also check the map option during the import to change the current values to the corresponding ids:
[JSWCLOUD-5942] Ability to create a sprint when importing from a CSV file
@david, can JiraSprintBuddy still be used seeing that password logon in Jira cloud has been deprecated for API?
Hello Mitch and Matt.
JiraSprintBuddy was a quick, weekend hack-together, so it's just written in PowerShell. There's nothing malicious in it, hence the reason it passes all virus scanners and Windows security checks.
David Bakkers, is the source for those buddy scripts available? Downloading unknown binaries is a bit risky
As a temporary work-around for this issue, I've created a small tool called JiraSprintBuddy that can import Sprints, with start and end dates, from a CSV file via the REST API. It can import Sprints into a single chosen board, or multiple boards via their ID. It comes with a User Guide and a template *.csv file.
Go here to download a copy.
My organization is attempting to migrate our projects over to jira. This issue is causing the worst problem with the migration.
1. I cant set up sprints when importing issues (not really important but would be nice)
2. I cant see the unique identifier of each sprint in the project, (important to easily import issues to project)
3. The ONLY way to find said unique value is to advance search each individual field value for each sprint (incredibly tedious and inconvenient, as I have set up 26 sprints and only through less than 25% of our projects)
This is a serious flaw with the import process and I hope that this is identified in future changes.
Hi everybody
I have the same problem. It is important that atlassian incorporates this functionality to be able to automate the creation of projects that already have a defined implementation scheme based on sprint.
We hope that it will be incorporated soon, dear Atlassians.
Almost 11 years later and there's no way to import sprint codes in bulk; or define them on issue import?
Hi All,
I am also facing the same issue while trying to migrate Jira Project to a new instance. To avoid Sprint Completion date issue, is it possible to update the database to add desired completion date for the Sprint ?
Thanks in advance,
Reshmi
Yep. It supports both Jira Server / Data Center with username + password and Jira Cloud with username + token.
Apr 2024 - I've just updated JiraSprintBuddy to v1-03 and made the following changes: