#1296 closed defect (fixed)
"Assign to" defaults to first registered user when using "restrict_owner = true"
| Reported by: | Juanma Barranquero | Owned by: | Christopher Lenz |
|---|---|---|---|
| Priority: | low | Milestone: | 0.9 |
| Component: | ticket system | Version: | devel |
| Severity: | minor | Keywords: | |
| Cc: | haircut@… | Branch: | |
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
[1342] is great and I've started to use it. However, some of my users complain that when restrict_owner = true, the Assign to: field defaults to the first registered user; they would want it empty, so reporters don't just blindly assume it's correct. And I tend to concur; I foresee a steady stream of tickets assigned to the poor fellow who happens to be our first alphabetically-positioned (or is that, alphabetically-challenged?) developer… :)
Perhaps a default_owner entry on trac.ini, defaulting to empty, would be in order.
Attachments (0)
Change History (4)
comment:1 by , 20 years ago
| Milestone: | → 0.9 |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
follow-up: 4 comment:3 by , 13 years ago
| Cc: | added |
|---|
Awesome! It looks like the change you made causes a blank at the top of the "Owner" dropdown list, correct?
Can you make this work similarly for the "reassign to" dropdown when modifying an extant ticket? That would make it possible to unassign tickets even when restrict_owner = true.
comment:4 by , 12 years ago
Replying to Adam Monsen <haircut@…>:
Awesome! It looks like the change you made causes a blank at the top of the "Owner" dropdown list, correct?
Can you make this work similarly for the "reassign to" dropdown when modifying an extant ticket? That would make it possible to unassign tickets even when
restrict_owner = true.
#6899 is the ticket you're looking for ;)
:-)
The default owner should be set from the component owner if the owner field is left blank. A
default_owneroption does not make much sense here IMO.