Opened 10 years ago
Closed 10 years ago
#11948 closed defect (fixed)
Upgrade db33 adds dead-end action to customized workflows
Reported by: | anonymous | Owned by: | Ryan J Ollos |
---|---|---|---|
Priority: | normal | Milestone: | 1.1.4 |
Component: | ticket system | Version: | |
Severity: | normal | Keywords: | workflow |
Cc: | Branch: | ||
Release Notes: |
In the |
||
API Changes: | |||
Internal Changes: |
Description
In #2045 the db33 upgrade was added that adds a <none> -> assigned
action. We had a slightly simplified custom workflow without an assigned
state. Now we have that dead-end action to assigned
, and tickets in that state can't be closed or "unassigned".
I assume for us the solution is to change the workflow again and remove that action, add a temporary unassign
action and unassign all tickets in that dead-end state.
But Trac should consider only upgrading default workflows or only actions to states that already exist.
Attachments (0)
Change History (4)
comment:1 by , 10 years ago
Component: | general → ticket system |
---|---|
Keywords: | workflow added |
Milestone: | → 1.1.4 |
Owner: | set to |
Status: | new → assigned |
comment:2 by , 10 years ago
Replying to anonymous:
I assume for us the solution is to change the workflow again and remove that action, add a temporary
unassign
action and unassign all tickets in that dead-end state.
User with TICKET_ADMIN
should have a special reset action, which allows tickets to be repaired when they are in states that are no longer defined. Documentation about the reset action has recently been added to TracWorkflow#BasicTicketWorkflowCustomization.
comment:4 by , 10 years ago
Release Notes: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Committed to trunk in [13728].
Replying to anonymous:
We can check that the
assigned
state is defined before adding the action.