Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Copilot Lvl 2
Message 1 of 3

Import issues & comment timestamps during migration

Solved! Go to Solution.

I'm spiking a migration of our private repos to Github from Bitbucket (source & bugs) and Trello (kanban boards). Also spiking Gitlab, we'll end up choosing depending on how much my team like the outcomes.

 

Obviously source is easy to move, no dramas there.

 

For accuracy of the historical record I need to ensure all the issues and comments have the original timestamps, and appear to be written by the original author (all of whom are also in the new Github org).

 

Seems like an obvious need, but I don't see anything in Github APIs v3 or v4 for creating issues with specified author and correct creation time.

 

I reckon I can overcome the authorship problem by collecting API keys from my users, but the timestamp problem eludes me. Can it be done? Or will we have to append the timestamps as crude plain text to each comment & issue?

2 Replies
Solution
Community Manager
Message 2 of 3

Re: Import issues & comment timestamps during migration

Thanks for reaching out and we're glad that you're considering GitHub.

 

There isn't a way to override the timestamps on issues via the API. Events will appear to have happened when the API request was submitted. You may want to add a standard block to the issues or comments using Markdown that gives the original timestamp for reference. Maybe something like:

 

> **Originally submitted at:** 2019-01-01 12:31:19

which would render like this:

 

Screen Shot 2019-09-25 at 3.56.08 PM.png

 

So hopefully less crude than you feared 😀

 

Let us know if you have more questions.

 

Copilot Lvl 2
Message 3 of 3

Re: Import issues & comment timestamps during migration

Hi @lee-dohm and thanks for your followup. The resolution in this case was all the boards stayed on Trello, and bugs will start afresh. Timeline and history matter, and losing that as structured data wasn't acceptable to the team.