Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#12794 closed enhancement (wontfix)

Separate User and Developer Issue Tracking Systems

Reported by: lazaridis_com Owned by: Dustin Machi
Priority: high Milestone:
Component: Operations Version:
Keywords: Cc:
Blocked By: Blocking:


The team should think about to provide a 2nd trac instance, which would be used by users.

Developers can concentrate better, as they don't get disturbed by trivial tickets or wrong tickets etc.! The ticket system is used to organize the work. Only committees and selected contributors get access - similar to the read-only developer list. Users have read-only access, so they see everything.

Users feel better, as filing tickets is not so "strict" and because the ticket-processing is more "casual". They would have the benefit of not having to deal with developers which are e.g. within a coding trap and loose their manners, trying to close tickets as fast as possible. Users could keep tickets for longer open as they wish.

The implementation is quit easy, as trac provides inheritance for the configuration files. The existent system stays as it is and becomes a development resource (no interruption of workflow), the new one becomes a user-resource (and inherits nearly every setting).

A copy function (accessible by the developers only) could automatically move an issue to the dev system.


Such a setup would avoid behavior on the project resources which can be conceived as rude (both, on user and on developer side), see e.g. those issues:

Think in a relaxed moment about how those "other users" may have felt. Additionally, the expectation those users have to the toolkit-functionality, can give worthfull insights on how to increase the usability of the toolkit.

(feel free to close this issue, but you should really think about it, as it is possibly the only way to please both sides. btw: I'll now stop filing issues for some time, as I move on to code level.)

Change History (2)

comment:1 Changed 8 years ago by bill

Resolution: wontfix
Status: newclosed

Thanks for the suggestion, but we talked about it in the meeting and we have no interest in setting up another trac instance.

comment:2 Changed 8 years ago by lazaridis_com

Ok, just one last thing for info:

I forgot to mention that another possibility is the use of the mirrors (e.g. the existent ones on github).

Note: See TracTickets for help on using tickets.