Labels
Labels
33 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
- 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)
- Issue declining to fix and will not work it
- Pull requests that update a dependency file
- Issue/PR for feature design documents
- Duplicates an existing issue either directly or indirectly
- 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.
- Issues which are ideal for a first time or new project contributor.
- Issues that can become a “good first issue” but need more description/context.
- Issues highlighted by lists for Hacktoberfest (https://hacktoberfest.com/)
- Pull Requests counted for Hacktoberfest (https://hacktoberfest.com/)
- Issues that are related to the transfer to Hiero
- Code changes driven by non business requirements
- Further development work cannot be done
- A new feature, service, or documentation. Major changes that are not backwards compatible.
- Issues that can be solved without coding like documentation.
- 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
- Further information is requested
- Behavior that used to work in a released product or service that no longer works with a new release.