Kallithea issues archive

Issue #129: issue tracking

Reported by: xd1le
State: open
Created on: 2015-05-02 09:38
Updated on: 2018-05-19 20:28


I may have missed it but it does not look like Kallithea currently supports issue tracking? If that is the case, then is it in the roadmap? Apologies if this has already been brought up, I could not see it anywhere.



Comment by Mads Kiilerich, on 2015-05-02 11:45

Some would love to see something integrated, most are very much aware that any builtin issue tracker most likely not would The One Tracker To Rule Them All and have their own preferences.

Anyway, noone has contributed issue tracking.

Comment by xd1le, on 2015-05-02 16:43

Thanks for the clarification. I feel like issue tracking is fairly integral to a software management system (and least something basic like whatever is used for these issues itself)? Would you agree? (Or is there another way to handle "issues", mailing lists even?)

If you do, what's your preference, integration (with kallithea)? Perhaps, would it even be possible to integrate an already existing tracker to kallithea?

Because, assuming you're a core developer for Kallithea, if you don't prefer an integrated tracker, then I see little point in keeping this issue open. (Unless of course someone else wishes to work on it.)

I myself prefer something integrated, imagining something relatively simple like Github's issue tracker.

Comment by xd1le, on 2015-05-02 16:44

Comment by Sean Farley, on 2015-05-02 17:21

FYI, @kiilerix is the project leader :-) My idea for a roadmap has been to make the issue tracker pluggable but to provide some kind of basic default. No idea about a timeline, though.

Comment by xd1le, on 2015-05-03 05:16

Comment by xd1le, on 2015-05-03 05:28

Thanks, yes I was looking at the log and saw his/her contributions and so assumed they might be integral to the project in someway.

I'm unfamiliar with bitbucket, is there a way to see all contributors and how many commits they have done? (I'm also unfamiliar with mercurial by the way, in case that doesn't make sense.) Also, you're listed as Staff, whereas @kiilerix is not, meaning are you bitbucket staff? :-)

Comment by Sean Farley, on 2015-05-03 19:00

Yes, he (Mads Kiilerix) is the project leader of Kallithea and a contributor to Mercurial. There isn't a way I know of to see contributor stats on Bitbucket (yet). And yes, I work for Bitbucket :-) I'm new, though, only been here a month.

Comment by Thomas De Schampheleire, on 2015-05-03 19:30

In Mercurial, viewing such commit shortlog can be achieved with the 'churn' extension (to be enabled in your .hgrc file). For example, to view an overview of all contributors since release 0.1, ranked by number of commits::

COLUMNS=80 hg churn --changesets --template '{author|person}' -r 0.1::

or between release 0.1 and 0.2::

COLUMNS=80 hg churn --changesets --template '{author|person}' -r 0.1::0.2

Comment by xd1le, on 2015-05-04 12:33

Awesome! Thanks for the info guys!

Comment on 2016-03-21 15:13

I currently use mercurial for my projects. I'd like to use a project manager to get a more efficient management. Kallithea looks interresting... but it is missing an issue tracker and eventually a wiki. In the front page of the Kallithea web site, it is written "You can integrate your instance with an issue tracker of your choice using JSON-RPC API and extensions interface." Any pointers on this ?

Comment by Mads Kiilerich, on 2016-03-22 20:53

The main issue tracker integration is the issue markup in the .ini .

The API stuff can be found on http://docs.kallithea-scm.org/en/latest/api/api.html ... but I don't know exactly what you should use it for.

The extensions interface is a bit odd, rough, undocumented and subject to change - it should perhaps not be mentioned that prominently. @andrew_shadura can you try to tweak the description?

Comment by Thomas De Schampheleire, on 2018-05-19 20:28

This is not more 'on hold' than other feature requests, so changing to 'open'