i tested the CSV import for worklogs in our testing environment and i saw that it gives you problems when importing to an issue that got moved.
i.e. in your CSV you got an entry for issue ABC-123 but the issue got moved in the meantime to XYZ-789. The importer won't give you any errors but afterwards the issue is not in the system anymore. JIRA will give you the "issue can not be viewed right now" screen.
Does anybody know about this behaviour or where the issue goes to?
Jira tracks the changes on all the fields, including the issue key, maybe you can do a script to update/resolve the issue keys of that list and then do the import.
If you try to access the issue page with an old issue key, jira redirects to the new issue key.
Hello, Community! My name is Gosia and I'm a Product Manager on Jira Server and Data Center here at Atlassian. Since 2002 when we launched our public issue tracker, jira.atlass...
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!
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