On 27 Dec 2017, at 1:51pm, Fredrik Gustafsson <iv...@iveqy.com> wrote:
> - What are our demands for a ticket system, would fossil or gitlab (for > example) suit us better? Here’s something from experience. You can have three types of ticket: A) Internal tickets. These are raised by employees of your company who understand your software, understand the ticketing system, and submit bugs only after they’ve done some forensic investigation to prove they are what they look like. B) External tickets, submitted by employees of your own company who may not really understand your software, may not be tech-clever, and may not understand how to investigate a bug. They are called 'the internal customer'. C) External tickets, submitted by people who don’t work for your company. If you have a ticketing system tied to your source depository, use it only for category (A) customers. If you want one for (B) and (C) (and you may not) set up a different one, with a web-facing GUI, which has no internal details (e.g. source code filenames) in. A customer of mine lost customer confidence because those customers got to learn too much about how their software worked, but not enough programming to see why things weren’t fixed the way they thought they should be fixed. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
