Labels
Labels
29 labels
- Issue is related to test case automation
- Automatically assigned when marking as blocked, needing client involvement.
- Automatically assigned when marking as blocked, needing developer involvement.
- Automatically assigned when marking as blocked, needing another issue to be completed first.
- Automatically assigned when marking as blocked, needing PM involvement.
- Automatically assigned to indicate this issue is a blocker for another issue.
- Something isn't working
- This issue should be included in the changelog / release notes
- A developer chore that does not have direct visibility for end users and so may not be testable
- Issue has been requested or reported by the client
- Severity: Affects critical functionality or critical data. It does not have a workaround.
- This issue requires designer work exclusively
- This issue requires devops work exclusively
- This issue already exists
- Modification to an existing feature
- A summary of a large feature that needs to be broken into several issues
- A new feature or a major change to an existing feature
- Issue describes functionality that is working as expected or will not be implemented as described
- Severity: Affects major functionality or major data. It has a workaround but is not obvious.
- Severity: Affects minor functionality or non-critical data. It has an easy workaround.
- This issue is for mockups only and will not go through the dev workflow.
- This issue still has mockups that are needed before development work can begin.
- QA needs to verify and update the issue before it can be worked.
- This bug exists on production
- Issue failed to meet the requirements set forth in it and needs additional work.
- This issue is a security-related concern
- Research only to look into the implementation methods, risks, and level of effort for upcoming issue
- Severity: It does not impact productivity or efficiency. It is merely an inconvenience.
- Our project documentation needs to be updated to include this new feature/enhancement