#12824 closed defect (fixed)
basic-workflow is not restored on environment upgrade
| Reported by: | Ryan J Ollos | Owned by: | Ryan J Ollos |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.3.2 |
| Component: | general | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: |
|
||
Description (last modified by )
The [ticket-workflow] section is restored on environment upgrade, if missing. While the basic-workflow.ini is used to create the environment, the original-workflow.ini is used on environment upgrade ([5731#file9]). The original-workflow.ini does not have a ticket create action (#2045).
It appears to just be a side-effect of the IEnvironmentSetupParticipant implementation that the [ticket-workflow] is restored after deleting it. The behavior is rather strange because most likely the user was running basic-workflow.ini or a custom workflow, but original-workflow.ini gets restored.
Proposed changes:
- DONE Add ticket create actions to
original-workflow.ini - Move handling of upgrade from pre-0.11 to a step in the upgrade module. comment:7:ticket:9023 is relevant to how we handle this.
- Either restore basic-workflow or do nothing when there is no
[ticket-workflow]section in trac.ini. #12642 will handle warnings when there are no workflow actions.
Attachments (0)
Change History (5)
comment:2 by , 8 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 8 years ago
| Milestone: | next-dev-1.3.x → 1.3.2 |
|---|---|
| Release Notes: | modified (diff) |
comment:4 by , 8 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Committed to trunk in r16010. I tested the upgrade steps from a 0.10.5 environment, upgraded to trunk (db44.py).



Considering something like these untested changes: rjollos.git:t12824_add_upgrade_steps.
original-workflow.iniwas fixed on 1.2-stable in r15969, merged to trunk in r15970.