• Table of contents
• Ticket templates
  • Product Backlog
  • Product Backlog ==> Sprint
  • Management
  • Bug
  • Feature
  • Support

Ticket templates¶

The following ticket templates are to give the team a jump start in making tickets that conform to our redmine documentation standards

Product Backlog¶

Large tasks that aren’t well defined and must be groomed.
(Note: product backlog items added by our client may not conform to our template)

h2. Problem/Motivation

(What / Why?)

h2. Proposed Resolution

(How?)

h2. Additional Information

(links to external files if applicable etc.)

Product Backlog ==> Sprint¶

A small task that is achievable by one team member, or a small task that must be completed by several / all team members. This will normally be a sub-ticket of a Product Backlog ticket added by the Product owner, and is used to define the effort-steps to complete the Product Owner's requirments.

h2. Problem/Motivation

(What / Why?)

h2. Proposed Resolution

(How?)

h2. Done Definition

# Deliverable 1
# Deliverable 2
# Deliverable 3 etc.

h2. Additional Information

(links to external files if applicable etc.)

Management¶

Used for documentation of internal meeting agendas and minutes.

h2. Agenda Topics

# Topic 1
# Topic 2
# Topic 3 etc.

h2. Meeting information

Date and Time: #th of Month, ##am/pm
Location: 
Duration: 
Meeting called by: 
Type of meeting: Weekly Meeting / Progress Meeting / Academic consultation / Conference Call
Note-taker: 
Attendees: 
Apologies: 

h2. Meeting Minutes

* *Topic 1*
*Discussion:*
> # Information 
p(((. *Conclusion:* 
> # Information 
* *Topic 2*
*Discussion:*
> # Information  
p(((. *Conclusion:* 
> # Information 
* *Topic 3 etc.*
*Discussion:* 
> # Information 
p(((. *Conclusion:* 
> # Information 

h2. Additional Information

(links to external files if applicable etc.)

Bug¶

An unexpected or incorrect result produced by the system.

h2. Summary

(What goes wrong)

h2. Steps to Reproduce

(How to make it go wrong)

h2. Expected Results

(What it should do)

h2. Actual Results

(What it currently does)

h2. Additional Information

(links to external files if applicable etc.)

Feature¶

Describes functionality needed by another team member’s module that they will need to implement.

h2. Problem

(What functionality is needed?)

h2. Motivation

(Why do you need it?)

h2. Relevant Technical Notes

(Any technical information that could help)

h2. Additional Information

(links to external files if applicable etc.)

Support¶

Used when in the process of a sprint and assistance is required from another team member.

h2. Problem/Motivation

(What / Why?)

h2. Relevant Technical Notes

(Any technical information that could help)

h2. Additional Information

(links to external files if applicable etc.)