Skip to main content

How to write good ticket

Opening a development task​

To open a new task go to the project, select the correct task list:

  • Create a new task with title and description
  • If you known the responsible for this activity, assign the ticket to him
  • If the developer can start to work on it, move it's column to "Approved for development"

Opening of a task due to an anomaly​

To open a new task go to the project, select the correct task list:

  • Create a new task with title
  • Add a description as follow:
    • Feature: describe the feature or the functionality where you encountered the issue
    • Expected Behavior: indicates what the expected result or behavior is for this feature
    • Current Behavior: indicates what happens now, which is the error that occurs
    • Steps to reproduce: indicates all the steps that must be taken to reproduce the error
  • If not pre-set and you known the responsible for this activity, assign the ticket to him
  • If the developer can start to work on it, move it's column to "Approved for development"

Sample ticket​

Title:
Iubenda popup non working

Description:
Feature:
Iubenda popup on terms and condition on registreation page

Expected Behavior:
when i click on the "terms and conditions" link i must see a popup with the text

Current Behavior:
when I click on the "terms and conditions" link the text opens to the full page and not in the popup

Steps to reproduce:
- go to homepage
- click on login
- click on register
- click on "terms and conditions"

Basic questions for opening an anomaly task​

  • Did the anomaly occur from desktop or mobile?
  • What browser are you trying with? (Firefox, Chrome, Edge ..)
  • What browser version (if known)?
  • What steps did he take?
  • What error is displayed?
  • (if applicable) Are you trying to upload a large file?
  • (If there are different environments) In which environment does the anomaly occur? (Production / Staging)

Working a development task​

  • If you have been assigned to a task, check if its status column is "Approved for development". If it's not "Approved for development", don't work on it, even if it's assigned to you.
  • Move the status to "Work in progress"
  • When you have finished, move the status into "To Test".
  • Log the daily spent hours on the task.
  • If everything works as expected, the project owner will move its status to "Done".
  • When the task is released into the staging environment, the project owner will move its status to "Staging".
  • When the task is released into the production environment, the project owner will move its status to "Production".
  • Only after being moved into "Production", the task can be closed by the project owner.