...
Jira is the system of record for all bugs, tasks, new features, improvements in Thalia. If we have an issue, no matter how trivial, we should create a jira record for it.
first pick the proper type:
- bug:A problem which impairs or prevents the functions of the product
- improvement:An enhancement to an existing feature. An existing feature or function of the product works as advertised, but you would expect more from it.
- new feature:adding significantly new portions of functionality to the product.
- task: anything else that requires the team member's time, like research, administrative work etc.
Pick a good summary:
When we're looking through lists of lots of issues, the summaries are essential in helping us to understand what an issue is about. Try to put as much detail as you can in the summary
Always choose a component:
If you can't find the right component, pick the closest one or discussing with QA to see if we need to create a new component.
Set the "Affects version"
please select the version of the product you were using where you encountered the bug or have the needs for new improvement/feature.
Set the "Fix version" to "triage"
everybody will have a chance to see it in the triage queue.
Write a detailed description:
For bugs, please put
1. Detailed steps to reproduce
2. What you expected to happen
3. What happened instead
4. contact person if the bug is from a customer.
For feature request and improvements:
1. detailed description on what needs to be done
2. why this new feature/improvement is important. what benefit will it give the users?
3. contact person if the request is from a customer
Link issues
Related issues should be properly linked. If a feature request can be split into sub requests, we should group them into sub-issues.
All new issues should have a component, a severity (can later be adjusted), version affected, and environment (OS and version, browser and version, Thalia version, etc), detailed description (If it is a bug, please list steps to recreate the bug). All new jira issues should have the fixed version set as "triage", so New issues will be triaged on a weekly basis or more frequently during the QA cycle. Triage meetings should be attended by both QA and developers. During the triage meeting, the issues will be assigned a fixed version, and maybe an assignee, and a priority. At the beginning of the sprint, during sprint planning meetings, product owner and the team member will reevaluate the issues for the current sprint.
After the sprint planning meeting, each developer is responsible for setting an time estimate and a due date for all his/her tasks.