I have moved scripts to new place

https://bitbucket.org/vrtareg/jira-agile-data-import/src/master/

If I understand correctly, sprints & ranking are imported for each project.

However when creating a board with multiple (imported) projects,

• JIRA creates several sprints i.e. one for each project
• The backlog is sorted by project first, then by priority i.e. global priority is lost

How can I deal with that? (except by merging projects before the export/import)

That is great. BTW just to share with you the latest version of Configuration Manager add-on supports migration of Agile Boards too. It works well and I have tested it but I would still be interested in doing it with own scripts.

Hi Ravi

I am on a final scripts check stage by Atlassian and I will share details soon.

Regards,
Areg

Hi Areg,

Would you be able to share the scripts so other can also get benefit with your solution

Hi

I have managed to do some reverse engineering and create script for Jira 6.4.x + MySQL combination to move Boards across.

Some manual work and running script recreates most of the information.

Will publish it soon somewhere ...

Regards,
Areg

We are not able migrate Boards

Aftering performing project import. The boards do not get recreated. That needs to be created manually and the sprints appear in the newly created board. Just make sure that the board configuration like filter, swimlanes and column are re-created exactly like source instance.

However in some cases people create multiple boards in the same project or use one board for multiple projects the sprint data doesn't seem to be migrated completely. I am working on such migration these days and will share the outcomes.

My reading of the source is that Rank order is preserved within each project, but not across multiple projects. I can't find the docs about the project importer and rank to add a comment there though

Is there any chance that this capability will be included in a 6.x release?

Hi,

When can we expect boards to be included as part of the project import/export as well as other Jira Agile data?

Understood, thanks for the info.

fool1629669540, we don't give ETAs for unreleased versions of JIRA. But you can see that the EAP for JIRA 7 is already out: https://www.atlassian.com/software/jira/download-eap so that should give you some indication of where we are in our overall process.

To clarify, we don't recommend that anyone use the EAP in their environments. These are unfinished builds intended for use by developers.

I'm also wondering if there is any ETA on when the JIRA -7.0.0 release is due.

THANKS! This is a HUGE improvement, and I appreciate all the hard work you put in

matt.doar, see https://developer.atlassian.com/jiradev/jira-platform/projects/guide-extending-the-jira-import-plugin

Kerrod, thank you for the update. Is there a process for add-ons other than JIRA Agile yet?

When is JIRA -7.0.0 release due?

This is pretty essential, IMHO.

I would wager a guess that a SIGNIFICANT proportion of JIRA users are using JIRA Agile too. If the plugin wasn't available then they wouldn't use JIRA, because Agile is the way they work. That is true for my usage. We're really buying JIRA Agile as "the product".

So being unable to migrate JIRA Agile projects is a serious short-fall.

Please could we get an update on progress? Thanks!

This is critical for me too. I know 'me too' comments are usually not appreciated, but it's getting quite hard for me to do my job with this stuff missing

For all the others frustrated by this (particularly for Jira Agile), it is actually possible to hack your way to import the contents of the Sprint custom field project by project

The following might help: https://answers.atlassian.com/questions/18448856/how-to-import-jira-agile-sprint-data-project-by-project

This is critical to us as well - status/update please?

I was told 1st semester 2015, is that still the target release date?

When is this will be available. It has been said that "this solution will not be available by the end of calendar year 2014" and we are in April 2015.

Any release schedule for this?

Thank you

This is a huge impact for other plugin developers. I have a plugin which stores only entity IDs in a custom field which are referenced in a Active Object table, where the names,etc. are kept. During a project import, all I can do is create place holder names for the imported entities using the old ID, and then manually rename these later. If only I had access to the activeobjects.xml in the Custom Field's project importer, that would at least allow me to parse it for my entries to get the field names, etc.

Randy,

Yes, that will work but there are so many thing to take care of. For example, the id of the boards, workflow statuses etc will change in the new environment. Your script should be able to take care of them.

We have done this for other customers and there is more to it than what meets the eye!

Can we get an ETA on this?

Also, is there a workaround? For example, can we completely rip out the agile stuff from the source jira, do the backup, import into the target jira, rebuild the agile stuff by hand in the target?

I would like to know if this is a workaround for this issue and how else can import the project?

Is there any workaround for this? Is is possible to migrate Rank and Sprint information for each issue via REST API?

More than 2 years? c'mon, you must be kidding!
First came Lexorank hell, now I stumbled upon data import blocker.
We've got Enterprise JIRA + Agile and this starts to be quite pain...

Hi there,
as our company setup consists of two different Jira instances - one inside and one outside of the DMZ - we must have an automatic synchronization of these two instances in place. Up to now an export/import mechanism is established that regularily syncs a subset of the issues in a bidirectional way.
The fact that Jira Agile data is omitted on export/import makes this issue a workstopper for us! Please add active objects support so that we can use Jira Agile for our projects. Operations is already looking for a Jira replacement product with agile support but we definitely want to stay with Jira!

Try to contact http://42picky.com/jira-consolidation/ as they do have experience with JIRA instance consolidation, ones with JIRA Agile on both sides. Note, only PostgreSQL is supported but you can always migrate to PostgreSQL before that, is the "standard" database for JIRA.

As we plan to migrate different instances into one in November 2014 we have the same problem as the others.
From the biggest instance we make a full import and the other instances we migrate via project imports. Our problem is that other projects also use Agile and with project imports the Agile data will not be correctly imported.

Is there a way or possibility to get around this problem in a month? Or do you already have a release date to fix this issue?
It’s very important for us to do this migration in November so we would be glad for any information.

@Jason Wong

Are you yet in a position to provide a further update w.r.t. the import of Agile between Jira instances?
You correctly state that this is very important to a number of us and I suggest that you might know whether a fix is feasible any time soon?

I am stalling on a merge between an on demand and a premise instance. We have jira agile in both and service desk in the on demand. We may be moving to portfolio as well, but I may discourage that for now since we cannot merge it either.

As I plan a migration here for the year end, I too require to import Agile projects from one instance to another.

Can Atlassian offer any form of work-around or commitment to support the import of Agile Projects in the near future?

I know what edit I'd like to see!

YOU WILL HAVE TO HAND EDIT THE XML FILE IF YOU WANT TO IMPORT YOUR PROJECT WITH JIRA AGILE DATA.

I'll let you add the details of what, precisely, we need to strip to make use of this critical workflow. Or maybe I will since I'm playing the whack-a-mole game to get a project imported (16hrs now to get one project from jira ondemand to jira on server ...)

Is this clear enough? I'm in a nightmare here.

bberenberg , I guess that the same kind of stressing as for that sentence would be more appropriate:

I think that something like this is more adjusted to the severity of this limitation:

I insist on stressing the impacts instead of the cause (active objects...)

rcorreia, can you please elaborate on the kind of edit you would like to see?

You should be able to proceed if you (at least temporarily) remove the plugin. At least that worked for me. (But as a disclaimer: We didn't use Agile before so it worked for us, but I don't know what happens when you already have agile data in the target jira and remove the plugin...)

At a minimum please update the documentation https://confluence.atlassian.com/display/JIRA/Restoring+a+Project+from+Backup

This line

"Project Import functionality does not currently include Active Objects data. This means data such as JIRA Agile sprints and Service Desk customer portals will not be included."

is NOT an Import Restriction it is a blocker for proceeding with Project Import. Please up-level it as such, that should take 30 seconds to edit the wiki page which requires 0 capacity. In fact give this account access and I will update it.

I feel like this ticket exists as their way of trolling everyone.

Would it work if the Agile Board is created and the sprints defined before the project and issues are imported?

If anyone has Sorin's (42picky) migration scripts, can you send them to me. My email is previous comment above.

Bam, this hit also me.

This is going to be a problem for my company as well. I have just been asked to merge our hosted jira with our premise jira (55 projects in our hosted jira). We need to import jira agile as well. Atlassian, please address this sooner or provide a legitimate work around without forcing us to relying on the user community to find a solution for you. Sometimes I think Atlassian takes too much advantage of the skilled user community.

42picky, can you email me your migration scripts at nancy.belser@inin.com? Thanks.

VZ Jira per-project migration of a very important project at my company is blocked at this time due to a known issue in Jira and Jira Agile:
https://jira.atlassian.com/browse/JRA-28748
https://jira.atlassian.com/browse/GHS-10577

I have contacted Atlassian Enterprise Support team with a priority 1 - highest level - request for a solution.

The information contained in JRA-28748 and GHS-10577 is not confidence building for me at this time.

I have undertaking a rapid and broad search for a workaround. At this time I have located unspecific mention of manual editing of the Jira database as a possible solution or partial solution. See 42picky added a comment - 14/Mar/14 8:38 AM above

I do not at this time know what steps are needed to perform the direct DB manipulation or how viable this is as a solution in general or specifically for my system and data. There is a risk of making a mistake in the database with an manual work performed there.

I am deeply disappointed in this lack of support for Jira per-project migration with Jira Agile plugin and the lack of support to solve this problem for almost 2 year from the time of first notice as referenced in JRA-28748, as well as, the response of the Atlassian Product Management team to seek and expedite a solution. So much so that I am sharing with you a link to the Executive Management of Atlassian as I feel it might in fact be best to seek to contact the executives directly to address this issue with Jira and Jira Agile per-project migration.

This has important consequences for managing large or complex instances of multi-jira environments as detailed in Special Note below.

Atlassian Executives and Board
https://www.atlassian.com/company/about/people

Special Note
The above blocking issue does not appear when doing a whole Jira site migration however a site migration will over-write ALL pre-existing Jira data in the receiving Jira site. This is a possible path to use but it will require a Service Window where JIRA will be down or at least locked so that backups can be run.

Then, ALL Jira parameters must be reconfigured for my Jira site. These include parameters such as all Users and Groups, email server settings, application linking settings between Jira and Confluence, and quite a few others.

As such, this path is not trivial and is at best only a worst case solution for my current Jira site which has only a few projects in it as this time. When my Jira site is a larger data set then the proceeding whole site migration will not be a viable solution. This has important implication for running a multi-Jira environment which is common for large groups.

Example multi-site Jira instances:

• Test / Develop Jira - not uptime sensitive. For testing upgrades, new plugins, and building new complex Jira
• Projects before deploying to the “Production” Jira.
• Production Jira - main system, stable releases, max uptime, work-critical for multiple teams.
• External Jira - for working with external vendors. Complete segregation from internal networks.
  Special Projects Jira - Teams with special needs that don’t fit in the Production Jira.

Ha! Give up!
We got licenses for JIRA back in January, put a ton of work moving everything onto it , only to find after the trial that our agile work couldn't be transferred onto our new system we had just paid for. WASTE OF MONEY!
We now use YouTrack. It's actually better. And it has a free plan. http://www.jetbrains.com/youtrack/
Save yourselves now, or sit in limbo forevermore.

Atlassian this appears to be very import bug, Please continue working to fix it

comment deleted.

42picky: We would be deeply appreciative of instructions on how to do this! Can you send us email at sysadmin@di2e.net? THANKS!

Perhaps you just haven't noticed the new information above:

— snip —
If you are looking for JIRA Agile specific data, we are tracking this separately here: https://jira.atlassian.com/browse/GHS-10577
— snap —

It's classified as "minor"!

All of you which think that this is a blocker for productaive usage of Jira Agile should vote for it and write their comments there, too.

see? even users are more willing to fix this than atlassian!