#1845 closed enhancement (wontfix)
"Assign to" Problem in Ticket Dialog
| Reported by: | anonymous | Owned by: | Jonas Borgström |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.8.4 |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description (last modified by )
I think it is a problem that "Assign to" is a textfield and not a combobox with all registered users. You can enter any string you want and the result is, that the ticket is may be assigned to a unknown person. The other problem is to know all names from the software developers of a big project…
Another problem is the centralized email notification problem. It should be possible to configure a mail address for every user. So it would be possible to send only a ticket mail to the person who is interested in it. The actual version can only send mails to a global mail distributor. This feature would only work if the first point is implemented!
The last problem is you want to assign a ticket to more than one person our groups of persons. May be it is possible to create user groups to which i can assign a ticket… The simple solution to add more persons would be to add 2-3 assign to comboboxes. The complicated solution is the creation of two text fields, one for the assign to persons and one for the list of the available users. Now the ticket creator could insert persons from the available user list to the assign to list…
Attachments (0)
Change History (4)
comment:1 by , 19 years ago
comment:2 by , 19 years ago
There is no description available for restrict_owner beside 1 comment which looks like a little bit strange. I tried to use the custom ticket fields without any result. But anyway thats not the 100% solution for me, because i want to have the list created automatically.
comment:3 by , 19 years ago
The restrict_owner setting is only available in trunk. You basically just set it to true and the field will become a list of all users that have logged into the system. So, I believe it does what you are asking for. See [1342].
comment:4 by , 19 years ago
| Description: | modified (diff) |
|---|---|
| Milestone: | 0.9 |
| Resolution: | → wontfix |
| Status: | new → closed |
All this is available in trunk and has been described in various other tickets (see for example #222).
About your last point: I think it'd be a bad idea to allow more then one owner for a ticket. Someone's got to be responsible for working on the ticket. Having multiple owners would confuse responsibility.
As for your first problem, just set the restrict_owner option to true in your TracIni.