Priorities should not be settable with new tickets

[stephen@…]

Is there a reason that the end user is able to set the priority on tickets? Having a priority distinct from Severity is useful for developers, but the end user shouldn't need to know (or be able to set) what priority a developer has over bugfixes, should they?

It's my opinion that having both present only serves to confuse end users, and should probably be left off…

[Manuzhai]

What, don't your developers ever open a ticket themselves?

[anonymous]

I also disgress. In our setup, the reporter from another department can indicate, how important the fix for the bug / the enhancement asked for etc. is for him.

[jordi@…]

Yep. I've always seen Trac as an internal tool. I don't like the idea of showing the Wiki, timeline, or source code browser to customers.

Around here at least customers don't use bug trackers. They call, or send emails to the helpdesk/person in charge. We input things in.

[anonymous]

End users should be able to have a way to input a ticket and gain information about it's progress. However, the email tool is probably the best way to do this.

[Matthew Good]

I think the above comments provide enough reasons to leave the priority available when creating tickets.