idea: add support for importing/sync'ing github issues

[jtriley]

I like the idea of gitissius, however, it doesn't quite solve the problem of users that wish to report bugs that are not themselves git users or experts. I think the github issue tracker is still the best way a new user that's unfamiliar (or uninterested) with git can report issues easily (assuming the project is hosted on github of course...). It would be useful if gitissius supported importing and syncing issues with github using the new github api using something like https://github.com/dustin/py-github

[jtriley]

Thinking about it a bit more even git users will need to have commit access to the repo in order to report bugs with gitissius. In the github case I guess you could fork and send a pull request on the gitissius branch but this seems very awkward to me....

So it seems unless you have direct commit access you can't report bugs easily with gitissius. Given this I think it'd be a huge improvement to add syncing with github issues or other external issue tracking systems as a mechanism for folks without commit access to report bugs.

[jtriley]

Of course it'd also be cool if github issues could create a 'gitissius'-like branch and store the issues there which would allow tools such as gitissius to easily parse and manage them. Perhaps @kneath would be interested in this idea?

[jinxcat]

Just chipping in...

What we have done so far is exactly what you described; fork the repo, create new issues, commit and issue a pull request to the origin "gitissius" branch :)

It's not that awkward really... give it a try ;)

[jinxcat]

Also, if you haven't noticed, gitissius uses gitissius for issue tracking ;)

[jtriley]

@jinxcat Thanks for confirming. Submitting pull requests to submit/manage issues seems like the same amount of work as submitting an issue on the web so I don't really see the advantage here.

I like the idea of gitissius' command line git-tracked issues, however, I just don't see the benefit until it can synchronize with a web-based user facing issue tracking system (preferably github issues). This way developers, and more importantly users, have the option of using the web when they're in a browser (like I am currently) or using gitissius when they're coding and still be working with the same set of issues.

With github issues you're forced to use the web (or at least the github api over the network) and with gitissius you're forced to use git/terminal - it would be nice to be able to handle both environments and keep them synchronized. I'm currently using github-cli to provide a command-line interface to github issues which works great except that you must be online obviously to manage issues. It would be nice to also have gitissius' ability to use git to allow offline issue browsing/management while storing the 'master' copy on github issues.

Just my two cents...

[glogiotatidis]

On Tue, 2011-11-08 at 14:09 -0800, Justin Riley wrote:

I like the idea of gitissius, however, it doesn't quite solve the problem of users that wish to report bugs that are not themselves git users or experts. I think the github issue tracker is still the best way a new user that's unfamiliar (or uninterested) with git can report issues easily (assuming the project is hosted on github of course...). It would be useful if gitissius supported importing and syncing issues with github using the new github api using something like https://github.com/dustin/py-github

---

Reply to this email directly or view it on GitHub:
#4

Hi Justin,

thanks for the idea. It's actually pretty cool and the py-github
interface looks ok.

The problem you are mentioning, that it is hard for users -or even
developers I would add- to submit bug reports or comment on existing
bugs, is something that I 'm already looking into.

I'm planning a service (gitissius.org) between the lines of
readthedocs.org, but for issues, which will enable users to have view
access to your issues through the web but also report new issues. What
do you think about that?

Glad you like the project, looking forward to hear more from you ;)

Giorgos Logiotatidis
[email protected]
GPG Key: 0x208A199F

[mcepl]

Just let me add here a bit of self-advertisement ... https://github.com/mcepl/github-issues-export is able to export to BE XML format (BE as http://bugseverywhere.org), and my #12 allows import from this format to gitissius (if somebody answers the question in that PR).

Also, I am now working on the github issues sync for BE in http://luther.ceplovi.cz/git/bugseverywhere.git/log/?h=pull-from-github which works in one direction (pull issues from github), but not yet other direction.