Project

General

Profile

Ticket templates » History » Version 2

ashley maher, 27/04/2021 09:47 AM

1 1 Peter Qian
{{>toc}}
2
3
h1. Ticket templates
4
5
The following ticket templates are to give the team a jump start in making tickets that conform to our [[redmine documentation standards]]
6
7
h2. Product Backlog
8
9
Large tasks that aren’t well defined and must be groomed.
10
(Note: product backlog items added by our client may not conform to our template)
11
12
<pre>
13
h2. Problem/Motivation
14
 
15
(What / Why?)
16
17
h2. Proposed Resolution
18
19
(How?)
20
 
21
h2. Additional Information
22
23
(links to external files if applicable etc.)
24
</pre>
25
26 2 ashley maher
h2. Product Backlog ==> Sprint
27 1 Peter Qian
28 2 ashley maher
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.
29 1 Peter Qian
30
<pre>
31
h2. Problem/Motivation
32
33
(What / Why?)
34
35
h2. Proposed Resolution
36
37
(How?)
38
39
h2. Done Definition
40
41
# Deliverable 1
42
# Deliverable 2
43
# Deliverable 3 etc.
44
45
h2. Additional Information
46
47
(links to external files if applicable etc.)
48
</pre>
49
50
h2. Management
51
52
Used for documentation of internal meeting agendas and minutes.
53
54
<pre>
55
h2. Agenda Topics
56
57
58
# Topic 1
59
# Topic 2
60
# Topic 3 etc.
61
62
h2. Meeting information
63
64
Date and Time: #th of Month, ##am/pm
65
Location: 
66
Duration: 
67
Meeting called by: 
68
Type of meeting: Weekly Meeting / Progress Meeting / Academic consultation / Conference Call
69
Note-taker: 
70
Attendees: 
71
Apologies: 
72
73
h2. Meeting Minutes
74
75
* *Topic 1*
76
*Discussion:*
77
> # Information 
78
p(((. *Conclusion:* 
79
> # Information 
80
* *Topic 2*
81
*Discussion:*
82
> # Information  
83
p(((. *Conclusion:* 
84
> # Information 
85
* *Topic 3 etc.*
86
*Discussion:* 
87
> # Information 
88
p(((. *Conclusion:* 
89
> # Information 
90
91
h2. Additional Information
92
93
(links to external files if applicable etc.)
94
</pre>
95
96
h2. Bug
97
98
An unexpected or incorrect result produced by the system.
99
100
<pre>
101
h2. Summary
102
103
(What goes wrong)
104
105
h2. Steps to Reproduce
106
107
(How to make it go wrong)
108
109
h2. Expected Results
110
111
(What it should do)
112
113
h2. Actual Results
114
115
(What it currently does)
116
117
h2. Additional Information
118
119
(links to external files if applicable etc.)
120
</pre>
121
122
h2. Feature
123
124
Describes functionality needed by another team member’s module that they will need to implement.
125
126
<pre>
127
h2. Problem
128
129
(What functionality is needed?)
130
131
h2. Motivation
132
133
(Why do you need it?)
134
135
h2. Relevant Technical Notes
136
137
(Any technical information that could help)
138
139
h2. Additional Information
140
141
(links to external files if applicable etc.)
142
</pre>
143
144
h2. Support
145
146
Used when in the process of a sprint and assistance is required from another team member.
147
148
<pre>
149
h2. Problem/Motivation
150
151
(What / Why?)
152
153
h2. Relevant Technical Notes
154
155
(Any technical information that could help)
156
157
h2. Additional Information
158
159
(links to external files if applicable etc.)
160
</pre>