All our work and communication happens on the project’s issues. Since we only pay for closed issues it is very simple for all members of the project to understand: no one will do anything without an opened issue. Since you will not be paid for it.
How to open an issue
When opening a new issue you will need to select proper template for the required issue type.
Please, note that issues without a template would be closed.
Each template has its own required parameters and some common parts for all of them. Head to the next section to learn more.
What each issue must contain?
- All issues must follow the same templates
- All issues must be self-contained. A reader should only have your issue to know what do you want and how do you want it done
- Each issue must have two roles: reporter and assignee, it does not matter if one person does cover two roles
- Each issue must contain the estimated time, without estimated time you will not get paid for completing this issue. Note that only architect can set and approve estimated time
- Each issue must have a single label (this is what is called a type)
- All issues should be SMART
Bugs happen. Whenever you find one - feel free to open an issue with
This type must contain several things:
- How it should be
- How it is now
- Steps to reproduce, note that without these steps it will be impossible to solve this bug
- Your environment: project version, OS type, etc
When to open this type of issues?
- When the business asks you to implement something
- When you see a space for improvement
Each feature must contain several things:
- A business task, why this feature is even required? This is the most important part. Without understanding the business task it is impossible to resolve a feature
- Is there any technical constraints? Something we should care about
See how to close issues.