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:

• Added - Option to log all API responses for debugging
• Changed - Removed the Jira type selection menu from the connection window
• Changed - Sprint names are always limited to 30 characters, to comply with Jira Cloud and Data Center limits
• Changed - No longers displays the Project Lead in the list of Projects

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

Any macos build for JiraSprintBuddy 

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

This issue is preventing my team from moving to JIRA. We have 2+ years of agile data and creating fake issues to create past sprints is too much trouble.
(also coupled with the inability to change sprint completion dates, which breaks reporting, as described in JSWCLOUD-11114)

Thanks for your solution Chiranjeevi. Yes indeed closing a sprint always picks up the current date so you're not able to show an accurate view of when you ended your sprint. This consequently affects the ability to display a sensible burndown chart.

I have created the sprints in the following way

1. i have created the custom field Sprint No and assign the sprint no for associated sprint names for each issue
2. After importing the issues , i will search the issues based on Sprint no using Quick filter
3. Created the sprints for those issues and start the sprint with the old start date and close date
4. only the issue is since it is old sprint while closing the close date of sprint is updating with current Date. 

Also worth mentioning, I couldn't import the sprint information for issues that had been carried over across more than one sprint. These issues would be associated with multiple sprint IDs and the sprint field in JIRA doesn't seem to understand the format.

I had the same issue.  I had to create a fake story in each of the sprints that were done to be able to mark them as started and then done.  I am sure it probably throws off the velocity because even through you put in the end date of the sprint, it measures until your marked it complete.  Then I would delete that story.

Using Sprint ID to do the mapping worked for me. I had to do it manually which isn't easy if you are importing many sprints. The sprints occurred in the past and the Sprint IDs created on the new JIRA instance are still waiting to be "started". They won't show any of the past tickets in their backlog if those are resolved or closed, but if you do a search for a Sprint ID it will return all the issues attached to it. Now I need to figure out how to start and end those Sprint IDs and hopefully this will recover the burn down charts.

This is so very frustrating that this cannot be mapped just by names.  This really is an impediment to migrations.  Please consider fixing this .  I have been online and have seen many issues associated with this.  Why not make migrations easier on people trying to migrate to your companies tool?

Some related links for sprint ID:
https://confluence.atlassian.com/display/JIRAKB/JIRA+Software%3A+How+to+search+for+a+Sprint+using+JQL
https://answers.atlassian.com/questions/31678219/how-do-i-know-the-sprint-id-number-of-a-current-sprint-
https://answers.atlassian.com/questions/19141129/how-to-get-sprint-id-for-csv-import

Kind regards,
Martin
JIRA Software

What is the best way to get a Sprint's ID?

How to get sprint ID number ?
We also has the same problem with new Jira 7.
thanks

madhusudhan.matrubhai - we regularly review the way we update and message issues here on jira.atlassian.com and will incorporate your feedback.

We have been improving the importers to JIRA and will continue to do so, please keep an eye on https://confluence.atlassian.com/jira/migrating-from-other-issue-trackers-119334.html for updates.

Regarding CSV imports, it is currently possible to map an issue to a sprint, but at the moment it is not easy or convenient. The sprint must already exist in JIRA and you would need to know their IDs.

I will reopen this issue to allow further discussion, however we cannot provide any guidance at this time as to when, or if, we'll be implementing this Suggestion.

Kind regards,
Martin
JIRA Software

@Michael Tokar, instead of classifying this as "Answered" can you make it as "won't fix".

we have no plans to implement this functionality in the next 12 months. If we do get around to addressing it, we will re-open this request or create a new one.

I don't understand how will you track this one when you closed it and how you will even know that this exists. This is totally ridiculous excuse I must say and you guys are not honest and transparent with your motives here unfortunately.

it is infeasible and disingenuous to our customers to keep them all open for an indefinite amount of time.

So this clearly shows that you guys are not on track to close all the open items and hence sweeping them all under the carpet as "closed".

We hope you appreciate our open approach to feature requests,

Open approach !! seriously !! what is open here about ??

It's unfortunate that this isn't important. This holds up merging off your competitors such as VersionOne and Rally as customers want their data mapped over. Without this option, many clients decline moving to your product.

helpdesk19 this issue was marked as "Answered" because, as my comment states above, we have no plans to implement this functionality in the next 12 months. If we do get around to addressing it, we will re-open this request or create a new one. With the high volume of requests we receive, it is infeasible and disingenuous to our customers to keep them all open for an indefinite amount of time.

If this outcome is not acceptable for you, you may want to reach out to our Experts. They may be able to assist you with a solution.

We hope you appreciate our open approach to feature requests, and we ask that you continue to give us feedback on the product!

Many thanks,
JIRA Agile Team

Why is this marked as resolved? Is there something I'm missing?

Many thanks for reporting this issue. Realistically, we are not planning on addressing it in the next 12 months.

Regards,
JIRA Agile Team

Hi Simon,

Is there any workaround?

Thanks,

Sam

This also applies to importing through Project Import

https://answers.atlassian.com/questions/87394/importing-from-csv-into-greenhopper-how-to-map-the-sprint-field