Changes between Version 3 and Version 4 of MilestonesAndTickets


Ignore:
Timestamp:
01/14/10 09:29:56 (12 years ago)
Author:
Josh Smift
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MilestonesAndTickets

    v3 v4  
    77  * Each milestone should have a ticket created for it once work has begun on it. 
    88  * Tickets can be used for many purposes.  Examples are:
     9    - Providing an update on progress of an open milestone
    910    - Requesting a change in milestone due date or language
    1011    - Identifying a dependency on another project
    11     - Providing an update on progress of an open milestone
    1212  * Anyone with a wiki account can create a ticket.  It is expected that project staff and the GPO will create and update tickets.
    1313  * It is important that the ticket is assigned to the correct ''milestone'' and ''owner'' and the GPO system engineer should be included under ''cc:''.
     14  * You should generally not change the Summary or Description field of a ticket except to make minor corrections like typos. If the task described on a ticket changes substantially, note that on the original ticket and create a new ticket with the new description.
    1415  * A useful view for checking the tickets associated milestones is [report:3 Active Tickets by Milestone].
    15   * Ticket associated with overdue milestones should be updated frequently (e.g., 2-3 times per month).
     16  * Tickets associated with overdue milestones should be updated frequently (e.g., 2-3 times per month).
    1617  * Only the GPO can mark a milestone as complete.  Once  a project believes it has achieved a milestone, an associated ticket should be updated to reflect the progress.  The GPO SE will get a copy of the ticket (see above).  If the system engineer agrees the milestone is complete, they will update the milestone entry and the listing on the project page.
    17   * To create a ticket that notes a dependency on another project, create a ticket, associate it with one of your milestones, assign the owner to be the PI of the other project, add text that describes the dependency.
     18  * To create a ticket that notes a dependency on another project, create a ticket, associate it with one of your milestones, assign the owner to be the PI of the other project, and add text that describes the dependency.