Tempo throws "Issue not found" error while adding tempo timelog against migrated tickets

[Balakumar Gopalakrishnan]

Hello Atlassian Team,

Recently we migrated JIRA projects to new account due to org restructuring. Migration activity completed couple of days back and we were able to view all the projects and tickets under new account. Now there are two problems,

1. I am not able to add timelog against a migrated ticket. But I am able to create timelog against newly created tickets.

2. We are missing past tempo timelogs. We exported tempo timelogs from previous account and trying to insert them into new account using createWorklog api. This API expects issueId to insert timelog, but the issueIds are changed during migration (as expected), only issueKeys are retained as it is. Now we are looking for APIs to find issueId from issueKey to fix the gape. Couple of questions here

• Is this the right way to migrate tempo timelogs or is there any better/easy way?
• Do we have any other API to submit timelog against issueKey instead of issueId?

Thanks,

Balakumar

[Brant Schroeder]

@Balakumar Gopalakrishnan I would suggest checking your projects permissions to see if they are setup so you can log time.  I would also reach out to Tempo support on how to properly migrate logged time.