Migrate Issue Tracker From GoogleCode?

[antidote]

I was wondering if there was any specific reason why the issue tracker is still on google code, it seems rather disjointed to have the project and issue tracker so isolated from one another. If there isn't any real reason, or if the reason is that there wasn't a way to move the tickets, I did find a python script that uses the gdata library to migrate them over:
https://github.com/alexrudnick/migrate-googlecode-issues

If you do have a reason, then by all means, keep doing what you're doing, it's obviously working for you ;P.  Thanks in advance for appeasing my curiosity.

[Jack Frost]

We're not happy with the tracker at GCode, but we're even less fond of the one on GitHub - hence we just stay there until we find something better. Migration is not the issue, the tracker is.

[antidote]

(12-29-2014, 08:31 PM)Jack Frost Wrote: We're not happy with the tracker at GCode, but we're even less fond of the one on GitHub - hence we just stay there until we find something better. Migration is not the issue, the tracker is.

That makes sense, I'm not too fond of github's issue tracker either. I had one setup on my own site before it was taken down, 
http://www.thebuggenie.com/

I liked it, and it's release staging was pretty useful. You could also probably use JIRA which seems to have become an industry standard. There is also Phabricator, which may be a better choice:
http://phabricator.org/

[Jack Frost]

I don't think there's any active stuff going on to actually use something else at the moment. Jira came up once, but nothing really came of our discussion back then.

[antidote]

That's a pretty good point, if you're not actively discussing it, then it's probably a non-starter at the moment, Google Code seems to be serving your purposes for the moment. I've had my question sufficiently answered, please lock this topic if you wish, and thanks for not assuming I was questioning your practices, I was merely curious.

[mbc07]

Moved to Site Feedback and Questions...