New ticket creation #
- Open github development project
- Click new ticket
- Choose ticket type (bug report, feature request, simple issue)
Please use bug report or feature request only. Please take a look at the description titles and follow instructions. It will take you couple minutes more to produce good ticket and might save a couple hours of talking, especially if engineer will start working with this ticket in 3-5 months.
If ticket related to another tickets please use Related #XXX, or Blocked by #XXX or Depends on #XXX in the ticket description. This will create nice structure between tickets:
Related link example in
Alexs ticket:
Ticket
#2264 automatically sees those cross links
Labels #
| Name | Desciprtion |
|---|---|
| Tech Enhancements | If ticket purely connected with technical improvement, refactoring |
| Bugs | Bugs, if something does not working properly |
| EndUser Enhancements | User faced improvements |
| Low-level Bugs & improvements | Bug or improvements which does not bring any big value for users of for engineers |
| EndUser Enhancements | User faced improvements |
| SEO, Marketing | SEO related tasks |
| Marketing | Marketing related tasks |
| IR | IR = Investor relations, anything related to IR team requests |
| Security & compliance | Technical security or legal compliance related issues |
| Stability | platform stability related tasks |
| Epic | Big feature or business request |
| Draft | Ticket still in progress |
| Change Request | Small changes, minor changes |
Project #
To set up correct project and correct sprint you need to take a few steps.
- Before you create a ticket go to project go to organization and choose development in
- once you saved the ticket, click on the array
near development project and choose current sprint
Milestone #
Choose milestone based on your task