Modify ↓
Opened 20 years ago
Closed 17 years ago
#2694 closed defect (fixed)
"Assign to" defaults to first registered user when using "restrict_owner = true"
| Reported by: | anonymous | Owned by: | Eli Carter |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.11 |
| Component: | general | Version: | 0.9.3 |
| Severity: | normal | Keywords: | workflow |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
Using 0.9.3 release, the restrict_owner bug seems to have come back from #1957.
Attachments (0)
Change History (5)
comment:1 by , 19 years ago
| Keywords: | workflow added |
|---|---|
| Milestone: | → 0.11 |
comment:2 by , 18 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:3 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
It's not entirely clear for me what is the problem here, seems like the automatic assignment of ownership on ticket creation would rather be due to the component ownership mechanism.
I see at least another related problem: with
restrict_owner == true, it's not possible to un-assign a ticket… I suggest adding a blank entry in the drop down list, which should probably be interpreted as a way to move the ticket back to the 'new' state.Anyway, this needs to be clarified at the occasion of the workflow changes.