Opened 17 years ago
Closed 12 years ago
#6899 closed defect (worksforme)
Cannot reassign to null
Reported by: | Owned by: | Christian Boos | |
---|---|---|---|
Priority: | low | Milestone: | |
Component: | ticket system | Version: | devel |
Severity: | normal | Keywords: | |
Cc: | trac-ja@…, haircut@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
When I reassign a ticket with [ticket] restricted_owner=true
,
it contains a empty entry on the head of list on 0.10.
But 0.11 is not contain that.
Do you change spec of this part?
Attachments (0)
Change History (10)
comment:1 by , 17 years ago
Owner: | changed from | to
---|
comment:2 by , 17 years ago
comment:3 by , 17 years ago
Status: | new → assigned |
---|
Similar issue with assigning a default owner of a component.
follow-up: 5 comment:4 by , 17 years ago
The default owner of a component is a separate issue: #6912.
I'm not certain we want to change this; with the configurable workflow in 0.11, there is set_owner and also del_owner. I don't see how deleting the owner and moving the ticket to the 'assigned' state makes sense. If there is a need for this, I think we'll have to add a set_or_del_owner action. But I suspect it would be better solved as having two separate actions available.
What workflow are you using, and what are you trying to do?
comment:5 by , 17 years ago
Replying to ecarter:
I'm not certain we want to change this
OK, I think that all tickets must have a owner, too. I just ask you a current spec. I shuld use MailingList, sorry.
A simple workaround:
- Create nobody user (realuser or entry of SESSION table).
- Set all component's
default_owner
to nobody.
:-)
comment:6 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | assigned → closed |
If there is a use-case where this is needed, reopen the ticket. Otherwise, I don't think we need a blank entry in the assign-to list.
comment:7 by , 13 years ago
Milestone: | 0.11 |
---|---|
Resolution: | wontfix |
Status: | closed → reopened |
I think this would be useful.
What to do if the ticket owner leaves the team?
comment:8 by , 13 years ago
Cc: | added |
---|
comment:9 by , 12 years ago
Milestone: | → next-stable-1.0.x |
---|---|
Owner: | changed from | to
Status: | reopened → new |
This could be fixed by adding a new operation clear_owner
:
[ticket-workflow] ... unassign = new,assigned,reopened -> new unassign.operations = clear_owner
With:
-
trac/ticket/default_workflow.py
281 281 for x in owners], 282 282 id=id, name=id))) 283 283 hints.append(_("The owner will be changed from " 284 "%(current_owner)s ",284 "%(current_owner)s to selected user", 285 285 current_owner=current_owner)) 286 if 'set_owner_to_self' in operations and \286 elif 'set_owner_to_self' in operations and \ 287 287 ticket._old.get('owner', ticket['owner']) != req.authname: 288 288 hints.append(_("The owner will be changed from %(current_owner)s " 289 289 "to %(authname)s", current_owner=current_owner, 290 290 authname=req.authname)) 291 elif 'clear_owner' in operations: 292 hints.append(_("The owner will be cleared")) 291 293 if 'set_resolution' in operations: 292 294 if this_action.has_key('set_resolution'): 293 295 resolutions = [x.strip() for x in … … 358 360 updated['owner'] = newowner 359 361 elif operation == 'set_owner_to_self': 360 362 updated['owner'] = req.authname 363 elif operation == 'clear_owner': 364 updated['owner'] = '' 361 365 elif operation == 'del_resolution': 362 366 updated['resolution'] = '' 363 367 elif operation == 'set_resolution':
(the first two changes are unrelated to the present feature request and will be committed first)
Maybe even "The ticket will have no owner" instead of "The owner will be cleared" ;-)
comment:10 by , 12 years ago
Milestone: | next-stable-1.0.x |
---|---|
Resolution: | → worksforme |
Status: | new → closed |
Argh, too much code there ;-)
There's already a del_owner
operation!
I'm having the same problem.