Labels

Relates to the Maven build process.

Relates to the client-side TypeScript/JavaScript code.

Relates to the webforj-addons-components module generally.

Related to issues/changes to documentation, such as updating or adding.

Relates to the webforj-addons-services module generally.

General testing infrastructure or cross-cutting test concerns.

Pull requests that update a dependency file

Pull requests that update GitHub Actions code

Pull requests that update Java code

Pull requests that update Javascript code

Must be fixed immediately (e.g., production outage, security flaw).

Important issue impacting core functionality or a significant number of users.

Nice-to-have, minor issue, or low impact. Address when time permits.

Standard priority. Important but doesn't block core workflows or major releases.

Ignores the PR for the release notes.

Shows that the issue or pull request is currently blocked by another issue or dependency.

The issue has been reviewed and confirmed as valid by the maintainers.

More information is required from the reporter to proceed.

Issue requires review by maintainers to validate and categorize.

Indicates that work on the issue or pull request has been paused and will be resumed later.

Indicates that the issue or pull request is currently being worked on.

Signals that the pull request is complete and ready for review by other team members.

Indicated backward-incompatible changes. This is crucial for release notes.

Indicates that an issue is a bug or a problem that needs to be fixed.

For maintenance, build, CI/CD, and bump tasks that aren't features/fixes, etc.

Pull requests that update a dependency file

Reserved for issues related to documentation, such as updating, adding, or clarifying documentation

Signals that the issue involves improving existing functionality.

Denotes that the issue is a request for a new feature or enhancement.

Indicates a fix to a bug or a problem.