Hi There,
I just found Trac, and as a Subversion user looking for a bug/issue
tracking system it looks very promising.
There is one feature which would be very useful in our situation, and
which Mantis has, that's the ability to set access levels, and
private/public flags for issues.
As far as I can tell Trac allows us to set which areas (wiki, source,
tickets etc) a user has access to, but not what they see within those
areas.
Ideally we need to be able to do that, for example if we take tickets...
Developers want to use tickets for very fine-grained details, to keep
track of all the improvements, bug fixes etc. They have the highest
permission and can see everything.
Support staff don't need details of every function under development and
every behind the scenes refactor. They need to see what is relevant to
their work, things that affect the customer.
Customers need to see their own private bugs/issues (note that this could
be used for tracking non software issues like problems with delivery etc.)
and also public issues.
Being able to raise or lower the access level of a particular tickets is
also useful, since you may decide that something should be made public, or
perhaps the opposite.
Is there any way to do this with Trac at the moment, and if not, how hard
would it be to implement?
regards
Jon
I just found Trac, and as a Subversion user looking for a bug/issue
tracking system it looks very promising.
There is one feature which would be very useful in our situation, and
which Mantis has, that's the ability to set access levels, and
private/public flags for issues.
As far as I can tell Trac allows us to set which areas (wiki, source,
tickets etc) a user has access to, but not what they see within those
areas.
Ideally we need to be able to do that, for example if we take tickets...
Developers want to use tickets for very fine-grained details, to keep
track of all the improvements, bug fixes etc. They have the highest
permission and can see everything.
Support staff don't need details of every function under development and
every behind the scenes refactor. They need to see what is relevant to
their work, things that affect the customer.
Customers need to see their own private bugs/issues (note that this could
be used for tracking non software issues like problems with delivery etc.)
and also public issues.
Being able to raise or lower the access level of a particular tickets is
also useful, since you may decide that something should be made public, or
perhaps the opposite.
Is there any way to do this with Trac at the moment, and if not, how hard
would it be to implement?
regards
Jon