Once we have a way of importing the data, then it will definitely be included. When that happens, there's going to be a lot of manual combing through the GitHub issues and matching them up with Joomlacode issues just because there's no automated method to do so. The hard part is going to be actually getting the data from there. If you know of any sort of API GForge offers to get it, then let me know. Otherwise, we'll need to coordinate with the PLT (probably Sam since he's had oversight on that site for a while) to get the data.

After having that data to merge, adding the additional fields is a piece of cake.

I guess the biggest question is do we add this architecture now or wait until we have the Joomlacode data to work with?

My vote is for adding it now so that we can experience the workflow.

As an possible intermediate offering, we would probably easily parse the Git Issue Title for the CMS tracker id in the format [#12345]? This would have the dual effect of encouraging folk to add the CMS Tracker ID to the Git Issue Title. Many have it already.

Consider it done.