I do not know about importing archived Issues but a Fossil Repository contains the issues alongside everything else (wiki, issues/bugtracker,...). Maybe merging and hosting a Fossil repository might be a solution?
On Sunday, March 22, 2020 at 3:21:43 PM UTC, Martin Blais wrote: > > I've quickly archived all the Beancount issues and the repo in prevision > of the Mercurial shutdown next week. > New changes will be lost. > It's possible to reimport them into another Mercurial project I think, > that's the easiest avenue. > I still need to figure out where this is all going to go. > As you can imagine, with all that's going on, I have even less time. > I'm not sure yet where the repo will live, will advise > > > -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to beancount+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/e6e3a348-eb56-4c2b-9efe-76223b16055c%40googlegroups.com.
