...
- Sandra or Kirk create a Topic, SAK-2000: Course Management for 2.4
- The developers and the business unit get together to create a set of Stories, SAK-2001 thru SAK-2008, which break down the effort into workable chunks
- SAK-2001: Map Course Management to our Materialized Views is estimated at 40 story points and commited to an Iteration.
- Jon grabs it off the wall, begins writing hibernate mapping files, adding new java files as a sub directory of course-management
- Jon creates an Asset SAK-2010: Course Management Changes for 2.4, and attaches it as an Asset to SAK-2001, the Story
- He checks in his changes and labels the subversion log comment with SAK-2010 and SAK-2000, the Topic
- He marks the Story, SAK-2001 to Programming Completed.
- The Iteration ends.
- Kirk and Sandra commit SAK-2002 to the next Iteration, and the process repeats, with one (or more) Assets created for each Story.
- Once all of this work is done under the Topic, then we can look under Subversion logs tab in JIRA and see all of the revision changes
- Also, we can look under each Asset and see all the revisions that are tied to that Abbsset.
- Note that the Asset should capture a reasonable unit of coding changes that can be rolled to Test, tested idependently, and then rolled to Prod.
- The important distinction between Assets and all the other JIRA types is that the Asset goes to a real work unit of work, which has been committed to Subversion.
Use Case #3: A trouble ticket/bug fix
...