Milestone closed_at date is wrong

Question

Opened this issue 2 years ago · 7 comments

Answer 1 · 2023-01-16T23:59:10.000Z

I now set both closed_at and updated_at, but after the import both show the time of import.

This seems to be a bug of the importer -- question for the GH migration team.

Answer 2 · 2023-01-23T09:40:48.000Z

This is important. Was the question asked to the GH team?

Answer 3 · 2023-02-04T22:06:45.000Z

So this is not fixed even in the import to GitHub.com.

Answer 4 · 2023-02-04T22:09:28.000Z

Yes. Out GH contacts indicate that it cannot be fixed.

After the import, I suppose we can edit the milestone description to include the correct closing date.

Answer 5 · 2023-02-04T22:15:54.000Z

The correct closing date is defined by some event in the repo or is a new information that we should fetch from trac?

Answer 6 · 2023-02-04T22:26:51.000Z

We have it in the migration archive, in these files:

Answer 7 · 2023-02-04T22:44:10.000Z

It's strange that GH cannot fix the obvious bug in their importer.

Hopefully we could edit the dates in an automatic way later.

Thanks.