Opened 15 years ago
Closed 15 years ago
#9067 closed enhancement (duplicate)
Scheduling Function
Reported by: | anonymous | Owned by: | Jonas Borgström |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | ticket system | Version: | |
Severity: | normal | Keywords: | scheduling, testing, deployment, needinfo |
Cc: | josh@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
It would be nice to see the addition of a scheduling function that would allow the assignment on the testing and deployment. This would allow an assigned 'project manager' or 'product manager' to assign a 'QA manager' to assign testing tasks to 'QA engineers'.
This would allow for the managers to also assign tasks leading to the deployment of a specific version of the software.
Attachments (0)
Change History (4)
comment:1 by , 15 years ago
Keywords: | needinfo added |
---|---|
Milestone: | 2.0 |
comment:2 by , 15 years ago
Yes, it would be similar to (on scheduling) to #4781 and for time tracking on the project #710 would work, as well.
I guess for testing and deployment, one could create a ticket, assign it to a specific QA engineer for testing as well as for deployment staff. There would be a need for a new field on the ticket information, for an 'Assigned Project Manager' and that would be who ever is in charge of the that milestone, which would mean there would have to be a milestone manager set for that.
So all, in all this is what I'm looking for:
- Assigning a 'Milestone' manger
- Assigning a 'Ticketing' specific manager, who is notified when ever something changes on it (status, new attachment, comments…)
- #1962, #4781 and #710 implemented to work with this function.
- On the roadmap page, it would show who the 'Milestone' manager is, for that milestone
comment:3 by , 15 years ago
Cc: | added |
---|
comment:4 by , 15 years ago
Component: | project → ticket system |
---|---|
Resolution: | → duplicate |
Status: | new → closed |
Closing the ticket, as it doesn't correspond to a specific feature to implement (too vague, and the eventual missing pieces are covered by the tickets already mentioned above).
I don't exactly understand what you're trying to achieve, but have you considered adapting the TracWorkflow to your needs?
For the scheduling part, maybe you were referring to something like #710 (or one of its many duplicate), or maybe even #4781…
Bottom line: this ticket in its current form is too vague, even for the 2.0, please try the above suggestions or if it's really a limitation in Trac, state better your requirements.