Skip to content

Labels

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.
  • An error that causes the feature to behave differently than what was expected based on design.
  • Issue/PR closed without resolution.
  • Issue/PR was resolved (work was done/merged).
  • Issue declined and will not be worked.
  • Pull requests that update a dependency file
  • Issue/PR for feature design documents.
  • Duplicates an existing issue either directly or indirectly.
  • A body of work that can be broken down into specific tasks.
  • An issue found after the feature was completed, but caught in a testing env prior to a prod release.
  • Enhancing an existing feature driven by business requirements. Typically backwards compatible.
  • Pull requests that update GitHub Actions code
  • Either a small change or a medium change concentrated in a single component.
  • Issues that can become a “good first issue” but need more description/context.
  • Issues shown by lists for the Hacktoberfest and made for newcomers to do the first contribution.
  • Code changes driven by non business requirements.
  • Pull requests that update Java 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, which must be completed in the milestone otherwise the release is at risk.
  • Required to be completed in the assigned milestone, but may or may not impact the release schedule.
  • Low priority issue. Will not impact the release schedule if not complete.
  • New issue that needs to be triaged by the team.
  • Issues related to performance concerns.
  • An issue raising a question requiring feedback or guidance.