committee/code-of-conduct

Denotes an issue or PR intended to be handled by the code of conduct committee.

committee/product-security

Denotes an issue or PR intended to be handled by the product security committee.

committee/steering

Denotes an issue or PR intended to be handled by the steering committee.

Pull requests that update a dependency file

Documentation requirements for deprecation/removal of components or APIs.

do-not-merge/blocked-paths

Indicates that a PR should not merge because it touches files in blocked paths.

do-not-merge/cherry-pick-not-approved

Indicates that a PR is not yet approved to merge into a release branch.

do-not-merge/contains-merge-commits

Indicates a PR which contains merge commits.

do-not-merge/hold

Indicates that a PR should not merge because someone has issued a /hold command.

do-not-merge/hold-from-release

Indicates a PR must remain in `development` only and must not go into `main` or `stabilization`

do-not-merge/in-review

Do not merge this PR. It is still being reviewed.

do-not-merge/invalid-commit-message

Indicates that a PR should not merge because it has an invalid commit message.

do-not-merge/invalid-owners-file

Indicates that a PR should not merge because it has an invalid OWNERS file in it.

do-not-merge/needs-kind

Indicates a PR lacks a `kind/foo` label and requires one.

do-not-merge/needs-sig

Indicates a PR lacks a `sig/foo` label and requires one.

do-not-merge/work-in-progress

Indicates that a PR should not merge because it is a work in progress.

This item is related to the AI feature.

feature/animation

This item is related to the EmotionFX animation subsystem.

This item is related to AR or VR features.

feature/asset-pipeline

This item is related to the asset-pipeline subsystem.

This item is related to the ATOM and 3D rendering subsystems.

This item is related to the audio subsystem.

This item is related to the AZ core engine support libraries.

feature/bluejay

Categorizes issue or PR as related to the Bluejay Design System.

Content relating to CMake or the overall build system of O3DE.

feature/cloud-service

This item is related to the cloud services.

feature/docs-cleanup

This item is related to the editor subsystem.

Content relating to the Gem system of O3DE.

feature/graphics/lighting

feature/graphics

feature/installer

This item is related to the installer feature.

feature/lyshine

This item is related to the UI (lyshine) feature.

feature/networking

This item is related to the client or server network code.

feature/physics

This item is related to the physics subsystem.

feature/prefabs

This item is related to the prefab system

feature/project-manager

This item is related to the project manager feature.

feature/python-bindings

This item is related to the python bindings.

feature/scripting

This item is related to the scripting tools.

This item is related to the O3DE as an SDK initiative.

feature/systems

This item is related to the systems feature.

feature/tech-art

This ticket represents cross functional tasks assigned to technical art.

feature/terrain

This item is related to the Terrain feature

feature/testing

feature/tools-ui

This item is related to the Tools UI, design system, or O3DE branding

feature/trackview

This item is related to the Trackview and cinematic feature.

feature/vegetation

This item is related to the Vegetation feature

feature/viewport

This item is related to the viewport

feature/website

This is an issue with the website, not the content

feature/whitebox

This item is related to the whitebox feature.

feature/2d-renderer

This item is related to the 2D renderer subsystems.

feature-need/awaiting-more-evidence

Feature: Unknown importance. Possibly useful but not yet enough evidence to actually get it done

feature-need/immediate

Feature: Immediate. Must be actively worked on as someone's top priority right now.

feature-need/important-longterm

Feature: Important over the long term but may not be staffed May need multiple releases to complete

feature-need/important-soon

Feature: Must be staffed / worked on either currently or very soon ideally in time for next release

good-first-issue

Issue ready for a new contributor according to the help wanted guidelines.

Issue that needs help from a contributor. Must meet help wanted guidelines.

kind/automation

Categorizes issue or PR as related to automation

Categorizes the issue or PR as related to a blog post.

kind/broken-link

Categorizes an issue or PR as related to broken links.

Categorizes issue or PR as related to a bug.

Categorizes issue or PR as related to cleaning up code process or technical debt.

kind/content-architecture

Categorizes issue as PR as related to the presented structure of documentation.

kind/contributing

kind/deprecation

Categorizes issue or PR as related to a feature/enhancement marked for deprecation.

Categorizes issue or PR as related to design.

kind/dev-documentation

Categorizes issue or PR as related to engine developer documentation.

kind/documentation

Categorizes issue or PR as related to documentation.

Categorizes issue or PR as relating to content edits only.

kind/enhancement

Enhancement to an existing feature

Categorizes issue or PR as related to a new feature.

kind/foundation

Must be addressed by the Linux Foundation governing entities.

Categorizes issue or PR as related to the installers.

Issue or PR related to only media in the documentation.

kind/onboarding

Categorizes issue or PR as related to onboarding ("day one") workflows

Reference materials for users.

kind/regression

Categorizes issue or PR as related to a regression from a prior release.

Task aimed at producing a research outcome rather than documentation.

Categorizes an issue that goes in the O3DE Public Roadmap

Content primarily focused on code samples.

Categorizes issue or PR as related to an test.

Request for an official tutorial to be maintained in the O3DE docs.

Categorizes an issue as related to a video submission.

Categorizes an issue or PR as related to the website itself.

Indicates a PR lacks a `kind/foo` label and requires one.

Indicates a PR lacks a `priority/foo` label and requires one.

Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Indicates an issue or PR lacks a `sig/foo` label and requires one.

Indicates an issue or PR lacks a `triage/foo` label and requires one.

This ticket requires UX to work on the design before it can be implemented.

Issues and PRs related to all platforms.

platform/android

Issues affecting content related to Android as a target platform.

Issues affecting content related to iOS/iPadOS as a target platform.

Issues affecting content related to Linux as a host or target platform.

Issues affecting content related to macOS as a host or target platform.

platform/windows

Issues and PRs related to the windows platform.

pr-ready-to-merge

Indicates that a PR is ready to be merged.

priority/blocker

Highest priority. Must be actively worked on right now as it is blocking other work.

priority/critical

Critical priority. Must be actively worked on as someone's top priority right now.

Major priority. Work that should be handled after all blocking and critical work is done.

Lowest priority. Work that may be scheduled

Issues or PRs related to the Programmer's Guide project.

release-blocker

Denotes a PR that is blocking the release from proceeding

release-note-action-required

Denotes a PR that introduces potentially breaking changes that require user action.

review-required

A PR which requires review before merge.

(Temp) Denotes an issue related to the Rev the Engine program

Categorizes an issue or PR as relevant to SIG Build.

Categorizes an issue or PR as relevant to SIG Content.

Categorizes an issue or PR as relevant to SIG Core

sig/docs-community

Categorizes an issue or PR as relevant to SIG Docs-Community.

sig/graphics-audio

Categorizes an issue or PR as relevant to SIG graphics-audio.

Categorizes an issue or PR as relevant to SIG Network.

Categorizes an issue or PR as relevant to SIG operations

Categorizes an issue or PR as relevant to SIG Platform.

Categorizes an issue or PR as relevant to SIG Release.

Categorizes an issue or PR as relevant to SIG Security.

Categorizes an issue or PR as relevant to SIG Testing.

Categorizes an issue or PR as relevant to SIG UI-UX.

Denotes a PR that changes 100-499 lines ignoring generated files.

Denotes a PR that changes 30-99 lines ignoring generated files.

Denotes a PR that changes 10-29 lines ignoring generated files.

Denotes a PR that changes 500-999 lines ignoring generated files.

Denotes a PR that changes 0-9 lines ignoring generated files.

Denotes a PR that changes 1000+ lines ignoring generated files.

Indicates that an issue or PR is actively being worked on by a contributor.

status/approved

Indicates a PR has been approved by an approver from all required OWNERS files.

Indicates this is not actively being worked on and is in the backlog.

Issues or PRs that are blocked by other issues or PRs.

status/blocked-on-dev

Documentation work that is blocked (or possibly blocked) on dev.

Issues opened for discussions and feedbacks.

status/duplicate

Issues and PRs that are duplicates of other issues or PRs.

Indicates that an issue or PR should not be auto-closed due to staleness.

Issues and PRs that are invalid.

status/investigation

Requires investigation to validate the issue.

status/needs-edit

An issue or PR that requires editing from a Copy Reviewer.

status/needs-testing

An issue or PR that is ready for testing verification.

status/needs-ux-review

The UX SIG needs to approve the UI/UX design for this feature before it can be merged.

status/not-reproducible

Indicates an issue can not be reproduced as described.

Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Denotes an issue or PR has remained open with no activity for 30 days and has become stale.

status/tech-approved

Technical reviewers have approved this PR.

status/ux-approved

The UX SIG has approved the UI/UX design for this feature.

Indicates an issue that can not or will not be worked on

triage/accepted

Indicates an issue or PR is ready to be actively worked on.

triage/declined

Indicates an issue is not accepted

triage/needs-information

Indicates an issue needs more information in order to triage

Tickets which were determined to need to be split in triage.

ui-ux/in-design

This ticket requires UX to work on the design before it can be implemented.

This is a temporary label that will be removed once data conversion is complete

This is a temporary label that will be removed once data conversion is complete

This is a temporary label that will be removed once data conversion is complete

This is a temporary label that will be removed once data conversion is complete

This is a temporary label that will be removed once data conversion is complete

This is a temporary label that will be removed once data conversion is complete

This is a temporary label that will be removed once data conversion is complete

This is a temporary label that will be removed once data conversion is complete

This is a temporary label that will be removed once data conversion is complete

WF8 This is a temporary label that will be removed once data conversion is complete

No labels found. Sorry about that.