Labels
Labels
39 labels
- Issues resulting from a code or process audit
- Work that needs to be done sometime in the future. No milestone assigned or not yet available.
- Further development work cannot be done
- Contains a breaking change that warrants mention in the release notes
- A error that causes the feature to behave differently than what was expected based on design docs
- Issue/PR closed without resolution
- Issue/PR was resolved (work was done/merged)
- Relates to Smart contracts
- Issue declining to fix and will not work it
- Pull requests that update a dependency file
- Issue/PR for feature design documents
- Improvements or additions to documentation
- Duplicates an existing issue either directly or indirectly
- New feature or request
- An issue found after the feature was completed, but caught in a testing environment.
- Enhancing an existing feature driven by business requirements. Typically backwards compatible.
- Pull requests that update GitHub Actions code
- Good for newcomers
- Extra attention is needed
- Code changes driven by non business requirements
- This doesn't seem right
- Pull requests that update Javascript code
- Further development work cannot be done
- A new feature, service, or documentation. Major changes that are not backwards compatible.
- Not resolvable due to the inability to reproduce the reported issue
- An issue impacting production environments or impacting multiple releases or multiple individuals.
- High priority issue. Required to be completed in the assigned milestone.
- Required to be completed in the assigned milestone, but may or may not impact release schedule.
- Low priority issue. Will not impact the release schedule if not complete.
- New issue that needs to be triaged by the team