You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

How to file an issue: 

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

Set the priority

  • *blocker: *Severe crashes and major deadlocks. User can't use the system and there is no workaround.
  • Critical: Crashes, loss of data
  • Major: Major loss of function
  • Minor: Minor loss of function, general annoyance, or other problem where easy workaround is present
  • Trivial: Cosmetic problem like misspelled words or misaligned text.

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.

Describe the environment:

OS and version, browser and version, Thalia version, etc

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.

  • No labels