Opened 7 years ago
Closed 4 years ago
#13351 closed defect (fixed)
MultipleWorkflowPlugin - JavaScript broken (and other issues)
Reported by: | Owned by: | Cinc-th | |
---|---|---|---|
Priority: | normal | Component: | MultipleWorkflowPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 1.2 |
Description
I cannot get MultipleWorkflowPlugin to work, quite simply :) My configuration:
- MWP 1.4.1
- Trac 1.2.2
- Three workflows - a default one, and two specialized ones
- All are based on a modified enterprise workflow
- All share a common starting point -
<none> -> new
- The two "specialized" ones include a
pending_approval
state between thenew
andassigned
states (where each ticket is firstly either approved or rejected by a user with a special permission) - The default workflow applies to the default ticket types (defect, enhancement, task). The specialized workflows apply to special types named "task-tba" and "enhancement-tba"
- All are recognized in the admin panel
- All are well-defined, AFAICT (may submit if necessary)
On this setup, I have two major problems:
- The JS code which dynamically changes the available actions on a "new ticket" page is broken. Whilst creating a new ticket, if I change the ticket type, the available actions either do not change, or the entire page element (with the radio buttons) disappears. Furthermore, for every such selection of ticket type (i.e. not actually submitting the change, just selecting a different option in the drop-down menu), a new ticket gets created in the background even before clicking "create ticket" - very strange.
- Even once the ticket is already created, has the appropriate ticket type and is in a state supported by all workflows (e.g.
new
, in my case), I can modify the ticket only using the actions from one workflow (the default one, even if the ticket type is e.g. "task-tba").
Generally, it seems I can only perform the actions in the default workflow regardless of the actual ticket type. I turned on logging at the warning level, but nothing shows up. I also tried adding explicit INI sections for all the ticket types (e.g. [ticket-workflow-defect]
etc.) - didn't help.
Any ideas?
I'm thinking 13106#comment:4 might have something to do with this, but I didn't go through the entire changeset (16598), so I'm not sure.
Attachments (0)
Change History (7)
comment:1 Changed 7 years ago by
comment:2 Changed 7 years ago by
MWP 1.4.1 Trac 1.2.2
I meet the same problem about before clicking create new ticket, the another new ticket created in the background.
comment:4 Changed 5 years ago by
I am having a related problem; i'm trying the demo "Requirement" workflow; i've created a Requirement ticket type.
If i try to create a new ticket, once i set the ticket type to Requirement, the action radio buttons dissapear.
comment:5 Changed 5 years ago by
Fix found, in my case the Requirement workflow was missing the create state:
[ticket-workflow-Requirement] create = <none> -> new create.default = 1
comment:6 Changed 5 years ago by
Cc: | Ryan J Ollos removed |
---|
comment:7 Changed 4 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
In [17782]:
- The problem with seemingly randomly created tickets should be fixed
- Same goes for sometimes missing action buttons
Correction: some of these issues are invalid. I didn't read the installation readme properly and forgot to change the
[ticket] workflow
property in the config. I apologize.(This "fixes" the issue about the available ticket actions being responsive to the chosen ticket type - both in the "new ticket" and the "edit ticket" scenario.)
However, the issue about the (randomly) disappearing radio buttons persists, and so does the (mis)creation of tickets before actual submission. I checked whether this happens only after enabling MWP - definitely seems so.