Opened 17 years ago
Closed 17 years ago
#5531 closed defect (fixed)
Tickets totally broken in r5693
Reported by: | dna | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | 0.11 |
Component: | ticket system | Version: | devel |
Severity: | minor | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
- When creating a new ticket it is counted and linked as closed in the roadmap view
- The "Active Ticket" query also don't find it
- The "Action" form fieldset of the ticket is empty
Attachments (0)
Change History (13)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Component: | general → ticket system |
---|
Hello,
my trac.ini for [ticket]
[ticket] default_component = General default_milestone = Milestone 1 default_priority = major default_type = defect default_version = max_description_size = 262144 restrict_owner = true workflow = DefaultTicketActionController
comment:3 by , 17 years ago
Yes, so you'll have now to use 'ConfigurableTicketWorkflow' instead of 'DefaultTicketActionController'.
Sorry for the inconvenience, but we felt that the new name was more expressive.
We should probably issue a warning if there's no action provider at all.
follow-up: 5 comment:4 by , 17 years ago
Well,
this works for a new ticket. Any idea how to get the others to a "active" state?
Btw, such a warning or a ini-upgrader would be nice to have.
comment:5 by , 17 years ago
Replying to dna:
Well,
this works for a new ticket. Any idea how to get the others to a "active" state?
There's a status fixer plugin in the sample-plugins/workflow directory. Until we have core setup to assist in this case, that's the way to fix those.
Btw, such a warning or a ini-upgrader would be nice to have.
Yeah, a warning would be good.
comment:6 by , 17 years ago
Severity: | normal → major |
---|
comment:7 by , 17 years ago
Milestone: | 0.11.1 → 0.11 |
---|
comment:8 by , 17 years ago
Milestone: | 0.11 → 0.11.1 |
---|
Please don't change milestones as anonymous and without a reason.
comment:9 by , 17 years ago
Component: | ticket system → admin/console |
---|---|
Owner: | changed from | to
Priority: | highest → low |
Status: | new → assigned |
Type: | defect → enhancement |
Version: | devel → 0.9 |
comment:10 by , 17 years ago
Component: | admin/console → ticket system |
---|---|
Owner: | changed from | to
Priority: | low → highest |
Status: | assigned → new |
Type: | enhancement → defect |
Version: | 0.9 → devel |
Undo recent anonymous changes
comment:11 by , 17 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
comment:12 by , 17 years ago
Resolution: | wontfix |
---|---|
Status: | closed → reopened |
Revert another anonymous change… (TicketButcher playing here)
We could add a warning:
-
trac/ticket/api.py
149 149 [TracTickets#Assign-toasDrop-DownList Assign-to as Drop-Down List] 150 150 (''since 0.9'').""") 151 151 152 def __init__(self): 153 ctrlr_names = [c.__class__.__name__ for c in self.action_controllers] 154 self.log.debug('ticket action controllers: %r' % (ctrlr_names,)) 155 default = 'ConfigurableTicketWorkflow' 156 if default not in ctrlr_names: 157 self.log.warning("default action controller '%s' not used", default) 158 152 159 # Public API 153 160 154 161 def get_available_actions(self, req, ticket): 155 162 """Returns a sorted list of available actions""" 156 163 # The list should not have duplicates. 157 164 actions = {} 158 self.log.debug('action controllers: %s' % (self.action_controllers,))159 165 for controller in self.action_controllers: 160 166 weighted_actions = controller.get_ticket_actions(req, ticket) 161 167 for weight, action in weighted_actions:
comment:13 by , 17 years ago
Milestone: | 0.11.1 → 0.11 |
---|---|
Priority: | highest → normal |
Resolution: | → fixed |
Severity: | major → minor |
Status: | reopened → closed |
Ok, the warning in the above patch was deemed to be too obnoxious for people using a non-default workflow on purpose. So I just kept the cleanup of the log.debug, and added the 'workflow' keyword so that people having the same kind of trouble with the workflow than the one reported in this ticket will be able to find this information more easily, see r6823.
Well, it works fine for me… any reason the action form fieldset might be empty for you?
e.g. what is your
[ticket] workflow
setting and if you're using theConfigurableTicketWorkflow
, what's your[ticket-workflow]
section in trac.ini?Ah, one possible (and likely) reason is the renaming of the
DefaultTicketActionController
toConfigurableTicketWorkflow
…