Modify ↓
Opened 15 years ago
Closed 9 years ago
#5287 closed defect (fixed)
how is this different from the TypedTicketWorkflow plugin?
Reported by: | anonymous | Owned by: | Cinc-th |
---|---|---|---|
Priority: | normal | Component: | MultipleWorkflowPlugin |
Severity: | normal | Keywords: | |
Cc: | Trac Release: | 0.11 |
Description
Attachments (0)
Change History (3)
comment:1 Changed 15 years ago by
comment:2 Changed 9 years ago by
Owner: | changed from Ermal Memushaj to Cinc-th |
---|---|
Status: | new → assigned |
comment:3 Changed 9 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
I added a brief explanation to the plugin description on the MultipleWorkflowPlugin page.
Note: See
TracTickets for help on using
tickets.
As far as I can tell, the difference is in how they are configured. For this plugin, your workflows are exclusive by default. That is, if you have a workflow section for a particuar type, all workflows and only those workflows from that section will be available for that type. If you don't have a section for this type, the default "typeless" workflows are used.
By contrast, TypedTicketWorkflowPlugin allows you to enable/disable actions per type at a finer granularity, but you don't have the exclusivity. That is, if I have certain workflow for "task" and certain workflow for "defect,feature", then for all the workflow that should *not* be visible to task, I have to explicitly say .ticket_type = "defect,feature" for each one.