Opened 15 years ago
Closed 14 years ago
#8854 closed enhancement (wontfix)
Milestones - linked to workflow & extra fields
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | none |
Severity: | normal | Keywords: | |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
We have a release coming up, which we will call "C&I - December 2009". This release is co-ordinated & managed by specific people carrying out specific roles. ie one person is to make sure all the release sign-offs are carried out, afterwards another person is used to make sure the release is carried out.
These are all "constants" for this release.
A solution would be to record the following against a milestone: "workflow status" & "user". This could then be used to provide "default" owner values for the tickets within the milestone when it reaches the defined "workflow status".
ie. We have workflow with status "prep-release". Now for this release "Biggles" is responsible for ALL tickets that get to this status. So if we could record "pre-release" and "Biggles" against the Milestone we could then use it as the default owner without relying on the users having to manually select a username.
Sounds simple… but then again I'm not a python programmer….
Attachments (0)
Change History (3)
follow-up: 3 comment:1 by , 15 years ago
Milestone: | → 2.0 |
---|
comment:3 by , 14 years ago
Milestone: | triaging |
---|---|
Resolution: | → wontfix |
Status: | new → closed |
Replying to cboos:
So it seems you're asking for TracWorkflow support for milestones.
Well, re-reading the description, it's not the case.
This seems a very specific need, you should probably (find someone to) write a plugin for this.
So it seems you're asking for TracWorkflow support for milestones.
There have been similar ideas floating around, but no formal ticket until now.
Yes, some second generation workflow system, for any kind of resources, would be great.