Opened 19 years ago
Last modified 6 years ago
#2045 closed enhancement
Ticket should be immediately 'assigned' after creation when assigned to the reporter — at Initial Version
Reported by: | Christian Boos | Owned by: | Christian Boos |
---|---|---|---|
Priority: | normal | Milestone: | 1.1.3 |
Component: | ticket system | Version: | devel |
Severity: | minor | Keywords: | workflow |
Cc: | andrew.c.martin@…, olemis+trac@…, ethan.jucovy@…, gary.martin@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
Long time ago, on the mailing list, I proposed a patch to immediately set the status of a newly created ticket to "assigned" if the reporter and the assignee are the same person.
This saves one step, as the next logical step would be to "accept" the ticket that the reporter has just created for himself.
Therefore I propose the patch once again, for discussion:
-
model.py
142 142 # Assume that no such component exists 143 143 pass 144 144 145 # If the owner creates the ticket, status is directly 'assigned' 146 owner = self.values.get('owner') 147 if owner and owner == self.values.get('reporter'): 148 self['status'] = 'assigned' 149 145 150 # Insert ticket record 146 151 std_fields = [f['name'] for f in self.fields if not f.get('custom') 147 152 and f['name'] in self.values.keys()]
Note:
See TracTickets
for help on using tickets.