Opened 12 years ago
Last modified 12 years ago
#10553 closed enhancement
[PATCH] Additional milestone operation for sample-plugins — at Initial Version
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | 1.0 |
Component: | contrib | Version: | |
Severity: | normal | Keywords: | patch workflow |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
We have following workflow in my company:
If a ticket is rejected (which means not fixed / implemented) it will be moved to a milestone 'rejected'. Thus we have clean milestones with only implemented features / solved bug fixes.
It would be nice, if this could be parametrized using Trac workflow. I have implemented this in attached file MilestoneOperation.py
. Maybe the attached file could be committed in sample-plugins
, when there are no further comments regarding better / nicer implementation.
Plugin description:
Sets milestone for specific status.
Example
[ticket-workflow] resolve.operations = set_resolution,set_milestone resolve.milestone = invalid,wontfix,duplicate,worksforme->rejected
When setting status to duplicate
the milestone will automaitcally change
to rejected
.
Note: if user has changed milestone manually, this workflow operation has no effect!
Configuration
Don't forget to add MilestoneOperation
to the workflow option
in [ticket]
section. If there is no workflow option, the line will look
like this:
[ticket] workflow = ConfigurableTicketWorkflow,MilestoneOperation
Plugin file for set_milestone operation