Opened 7 years ago
Closed 6 years ago
#13086 closed enhancement (fixed)
Workflow status change should be an explicit operation
| Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.5.1 |
| Component: | ticket system | Version: | |
| Severity: | normal | Keywords: | workflow |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: |
The workflow state keywords |
||
| Internal Changes: | |||
Description (last modified by )
Discussed in comment:7:ticket:13013 and comment:8:ticket:13013 are two ideas for improving the status change behavior:
- Move status change operation to
trac/ticket/web_ui.py - Add a
set_statusoperation for explicitly controlling status changes.
Attachments (0)
Change History (9)
comment:1 by , 7 years ago
comment:3 by , 6 years ago
| Description: | modified (diff) |
|---|
comment:4 by , 6 years ago
| Milestone: | 1.3.5 |
|---|---|
| Resolution: | → wontfix |
| Status: | assigned → closed |
I've explored some changes, but I have no definitive ideas for improving on the design.
comment:6 by , 6 years ago
| Milestone: | → 1.5.1 |
|---|---|
| Resolution: | wontfix |
| Status: | closed → reopened |
Reopening to investigate moving ticket status change to trac.ticket.web_ui.TicketModule.get_ticket_changes (comment:2:ticket:13199).
comment:7 by , 6 years ago
I found what I think is a better way to implement r16954. Proposed changes in log:rjollos.git:t13086_move_status_change.2.
comment:8 by , 6 years ago
| Status: | reopened → assigned |
|---|
comment:9 by , 6 years ago
| API Changes: | modified (diff) |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |



I think the
set_statusoperation is redundant. When a new status of action is not*, that means setting a new status. Even thought a user don't specifyset_statusoperation, we have to set the new status.