Modify ↓
Opened 18 years ago
Last modified 10 years ago
#7176 new defect
Workflow actions indistinguishable from user changes
| Reported by: | Eli Carter | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-major-releases |
| Component: | ticket system | Version: | devel |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
- someone writes a workflow action that modifies a user-modifiable ticket field
- user selects that action, and previews the change
- user selects a different action
- user previews or submits changes
The changes made by the workflow action will still be present; they will not be reverted.
Internally, the code does not differentiate between user changes and workflow changes across a preview.
The correct behavior here, particularly in cases where the user modifies the same fields as the workflow, is open for debate.
Attachments (0)
Change History (3)
comment:1 by , 15 years ago
| Milestone: | next-minor-0.12.x → unscheduled |
|---|
comment:2 by , 15 years ago
| Milestone: | unscheduled → next-major-0.1X |
|---|
comment:3 by , 10 years ago
| Owner: | removed |
|---|
Note:
See TracTickets
for help on using tickets.
Actually the problem Eli described here is a known short-coming of the current TracWorkflow design. It was already discussed at length in some other tickets and this ticket is a summary of the problem. Definitely something we should address "one day".