project import - issues linked in target instance that are not linked in source instance

We are in the process of migrating a dozen projects from one instance of JIRA to another.

I'm using the botron configuraiton manager to move the workflows, custom fields, schemes, etc. Then using project export on the source JIRA instance and project-by-project import on the target instance.

Everything looks good. The only odd discovery made by our testers so far is they found (at least) two issues in the target instance that are linked to each other and are not linked in the source instance.

Even odder, in the history of both tickets, there is no history of creating that link.

For the links that are correct the history shows the link being created a month ago in the source directory. Then it shows it being created again after the project import. All looks good.

Any ideas?

Thanks!

3 answers

Did you do a full-index in the target instance after importing to the target instance? Usually that takes care of the issue you are having.

Mehmet

Just tried that. No luck.

You see anything weird in the logs?

I imported 18 projects. The logs are pretty verbose. When I get a few minutes I'll see if there's anything that pops out. thx

Here's a lot more data.

Further research on the links in DMO-460
* In Source, there are two links in the ticket, one is to TEST-1213 (also in destination) and one is to DIB-1765 (not in Destination)
* In Destination, there are also two links, TEST-1213 and MACE-1707.
* This history in both systems is identical. JoeBob created the link to DIB-1765 on 7/11 and Thomas created the link to TEST-1213 on 7/25.
* In destination DIB-1765, no links are shown, and yet there are two links in the history prior to the import. The history is identical to the source history, where the two links are shown.

A timeline

1445 - TEST-1213 imported
1524 - MACE-1707 imported
1711 - DIB-1765 imported
1727 - TEST-1213 was linked to DIB-1765 (this shows up in the history for TEST-1213 but not the history for DIB-1765) This is a link that should be appearing in both tickets and does not appear in either.
1828 - DMO-460 imported
1834 - TEST-1213 was linked to DMO-460. This appears in the TEST-1213 history, but not in the DMO-460 history. This appears correctly in both tickets.

There is no import history that shows the creation of the link between DMO-460 and MACE-1707. A link that should not be there but appears in both tickets.


There is no import history that shows the creation of the linke between MACE-1707 and TEST-1213. A link that should not be there bu appears in both tickets.

|| Ticket || No. of links in Source || No. of links in Destination ||
| DMO-460 | 2 | 2 |
| DIB-1765 | 2 | 0 |
| TEST-1213 | 2 | 2 |
| MACE-1707 | 4 | 6 |

So we have the correct number of links but they are misplaced.

Missing links:
* DMO-460 and DIB-1765
* TEST-1213 and DIB-1765

Added links:
* MACE-1707 and DMO-4690
* MACE-1707 and TEST-1213

It's as though MACE-1707 got the links that DIB-1765 should have had.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Sunday in Agility

You asked for it, so we delivered: images on issues have arrived

A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...

631 views 3 11
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