Modify ↓
#12807 closed enhancement (fixed)
Make it easier to customize the allowed owners for a ticket
| Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.3.2 |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | workflow |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: |
Added |
||
| Internal Changes: | |||
Description
I've been reviewing FlexibleAssignToPlugin and looking at how we can provide equivalent functionality in Trac. It appears it can be done by simply adding a get_allowed_owners method to ConfigurableTicketWorkflow. Users wishing to programmatically control the allowed ticket owners can subclass ConfigurableTicketWorkflow and override the method.
Attachments (0)
Change History (5)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
| Component: | general → ticket system |
|---|
comment:3 by , 8 years ago
| Keywords: | workflow added |
|---|
comment:4 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Added tests and committed to trunk in r15910.
comment:5 by , 5 years ago
Note:
See TracTickets
for help on using tickets.
Proposed changes in [86bacacb/rjollos.git].
Regarding the get_allowed_owners and eventually_restrict_owner
TicketSystemmethods, those are used to control the population of the select boxes on the query page and ticket admin components page, and create a list of valid users to complete the trac-admin componentaddandchowncommands. I think we should consider changing the behavior when implementing #7628. Rather than having a select box we can autocomplete the fields to a list of all possible owners. For the query page, that would be the set of all ticket owners. For the component owner field, that can just be all known users. If those changes are made, the methods will be unused by Trac and can be deprecated.Documented: