-
Notifications
You must be signed in to change notification settings - Fork 0
Issues
To navigate to the Issues, use this link
An issue can be created to document bugs or request new features. Please check that the issue does not already exist to avoid duplicates.
All issues should follow a common template setup. These templates are outlined below.
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
Expected behaviour / Acceptance Criteria A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- OS: [e.g. iOS]
- Browser [e.g. chrome, safari]
Additional context Add any other context about the problem here.
Related issues Reference related issues here
Description A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Acceptance Criteria A clear and concise description of what you want to happen.
Pointers / Solutions A clear and concise description of any alternative solutions or features you've considered.
Additional context Add any other context or screenshots about the feature request here.
Related issues Reference related issues here
Issues require a minimum of three people to review. When the final person reviewing approves the issue, it is their job to add the approved tag to the issue. Remember to test the issue exists against the latest version and that the details and estimations of size are appropriate.
Copyright © Team Project Hype-r Phlame. 2019. All Rights Reserved.