How to create a project with its history? i.e. completed sprints, etc.


We want to move from HP AM to Jira but unfortunately this is not straightforward. First, because there is no CSV export usable from AM. So we decided to do it by hand i.e. recreating previous sprints, main stories, etc. As the result was not conclusive, we even tried exporting/re-importing stories, a few updates in the DB, etc.

Here is our current situation and our problems:

  • All burndowns are flat i.e. 0 story points 
  • All sprint reports are flat (i.e. 0 story points) while the list of stories is good and the total story points displayed per sprint is also good
  • The velocity report does not show any completed points but commitments are good
  • The release burndown stacks all story points into the current active sprint and cannot display any forecast because "it needs at least 3 completed sprints"

I've seen a lot of threads related to one or another of these problems, so let me add a few remarks:

  • All sprints have correct start/closed dates
  • All stories have a status done which is well defined in the right column of the workflow.
  • All stories have a created date < start date of the sprint and a resolved date < closed date of the sprint

So yes, it's a real mess! But we don't see anymore solution to our problems. Is there any documentation on how to start a project with an existing history? Is there any way to solve our problems (even by updating the db)?

Thank you


burndown.PNGSprint report.PNGVelocity.PNGRelease.PNGissue.PNG

1 answer

0 votes
Thomas Deiler Community Champion Feb 05, 2018

Dear @xavier le galles,

for sure there is always a way - it just a matter of resources.

As you have the data already  in Jira, you need to fix the dates manually. At all, this means modifying Jira's database without Jira.

Before you do, make a backup, shut down jira and know the risk - you could destroy everything or bring the DB in an inconsistent state.

Or better, make an offline copy of the db, so you can do everything without a hurry.

Then use a tool like PL/SQL Developer to access and browse the database. Best you do this in a pair - four eyes see more.

Alternatively you can do this with a full backup of Jira - modify the XML. That depends on your abilities, where you feel more comfortable.

So long


Hi Thomas,

Thank you for your answer but we already tried it and did not have much success. For instance, all dates for sprints are right but stories are not taken into account: the list of stories per sprint is also right but it does cumulate their story points...

We have just an inconsistent state and I do not know where to start from. It is not a question of time/resources but more a question of documentation: there are tens of tables in this Db...

What I mean, is that there is no obvious error. If you don't know what you're looking for, you can waste hours in this database.
If at least I could log the queries made by each report, I could understand what is wrong?

Thomas Deiler Community Champion Feb 05, 2018

Jup - the db design is a little bit complicated. And more like a forest than a tree. ;) To be honest, I have no better approach ...

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,708 views 17 21
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you