I added a sheet that starts to shape this into the structures that trac can import:
* milestones, which have name, description, and due date (and a few others)
* tickets, which have #, summary, description, milestone, component, owner,
reporter
* tickets can also have blocked-by/blocking relationships. See, for
example, dependencies for
ticket:1<http://informatics.gpcnetwork.org/trac/Project/depgraph/ticket/1>
I adopted the following rough correspondence:
* Objective number -> milestone name
* though we don't use milestone names that imply order, since milestones
can be rescheduled and having milestone 2 before milestone 1 is confusing
* We've adopted a convention of using lakes and rivers in the greater
plains for milestone names
* Objective -> milestone description
* Work item number -> ticket number
* but trac ticket numbers are just serial numbers, so 1.1.6.1 would just
become 37 or some such
* Work item -> ticket summary
* Applicable -> owner
* the owner of a ticket is the person who has the ball to take the next
step, not necessarily someone with overall responsibility
* if we need to track overall responsibility, reporter would probably be
the best fit
* Timeline -> blockedby
________________________________
From: Greater Plains Collaborative Software Development
[[email protected]] on behalf of Campbell, James R [[email protected]]
Sent: Thursday, January 16, 2014 9:25 PM
To: [email protected]
Subject: Draft worklist and timeline development for data standardization;
4Public
In followup to our discussion of Wednesday 9AM, can I ask the data
standardization group (and our PI RW) to review this draft workplan for our
data standardization objectives and to comment back to me for edits so that I
can ask Dan to start organizing our activities in TRAC.
...
worklist-trac.xlsx
Description: worklist-trac.xlsx
