From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] Ticket tracking system for LTP
Date: Mon, 9 Apr 2018 17:17:38 +0200 [thread overview]
Message-ID: <20180409151738.GA2522@rei> (raw)
Hi!
Recently, as there has been more people working on LTP in SUSE than
myself, we started to accumulate LTP TODO items in our internal tool.
These include general ideas about LTP improvements, missing coverage,
broken tests, etc.
Keeping this backlog behind closed door is unhealty for upstream project
so I'm looking into some kind of system to track these where everyone
can create new tickets/bugs/issues whatever it is called and act on
them.
The main problem here is to choose right tool for the job, which is the
main reason for this email. I would like to avoid clumsy solutions such
as wiki table or a spreadsheet (I've been there and it was painful even
for a team of two people).
Here are some requirements I came up for it:
* Supports creating/commenting/closing issues/tickets/bugs or
whatever is single smallest entity is called as by anybody (possibly
after a simple registration)
* Should be reasonably simple and be able to handle >100 of open
issues, which I suppose rules out things that are tailored to be
used to support agile workflow such as trello that would end up
visually incomprehensible
* Should have basic text search capabilities
* Ideally we will not maintain the instance ourselves
- that rules out things like redmine unless there is
an instance we can easily tap into
* Data export is a plus
- I want to avoid situation where we loose our data
after a database corruption
* Should be reasonably estabilished
- I want to avoid a situation where we start to use some tool only to
find it has been discontinued half a year later
* Ideally it should be opensource
- however beggars can't be choosers we use GitHub quite extensively
after all
There is a list of poissibilities I have so far:
* GitHub issues
- probably the easiest solution
- we can create a specific labels to sort these out
- needs GitHub account which everybody has already
- some operations could be done only by LTP project members
I'm not sure if random users can add labels for example
* Some instance of Bugzilla
(maybe bugzilla.kernel.org if we happen to get LTP category there)
- while this would be OK for missing coverage and broken test
I find bugzilla clumsy general ideas tracking
* I've been told that JIRA is free for opensource projects but I have no
idea how the tool works or if it's at least reasonable fit. I looks to
me like it has far to many features we do not need at all.
* ??? (anything else any of you can think of?)
Rant: Actually I'm a bit disappointed that there is no command line tool
similar to taskwarrior.org maybe with a git backend for this kind
of backlog/team management...
--
Cyril Hrubis
chrubis@suse.cz
next reply other threads:[~2018-04-09 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-09 15:17 Cyril Hrubis [this message]
2018-04-11 13:15 ` [LTP] Ticket tracking system for LTP Sebastian Chlad
2018-04-23 13:38 ` Dan Rue
2018-04-24 8:48 ` Cyril Hrubis
2018-04-24 13:42 ` Petr Vorel
2018-04-24 13:44 ` Cyril Hrubis
2018-04-24 14:04 ` Petr Vorel
2018-04-25 14:29 ` Cyril Hrubis
2018-04-26 1:44 ` Sandeep Patil
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180409151738.GA2522@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox