Labels

Server environment. With good QA, you’ll identify issues on test and staging deployments.

Server environment. With good QA, you’ll identify issues on test and staging deployments.

Server environment. With good QA, you’ll identify issues on test and staging deployments.

Requires further conversation to figure out the action steps. Most feature ideas start here.

Requires further conversation to figure out the action steps. Most feature ideas start here.

No action needed or possible. The issue is either fixed, addressed better by other issues, or just out of product scope.

No action needed or possible. The issue is either fixed, addressed better by other issues, or just out of product scope.

No action needed or possible. The issue is either fixed, addressed better by other issues, or just out of product scope.

If the repository covers multiple parts, this is how we designate where the issue lives. (i.e. iOS and Android for cross-platform tablet app).

If the repository covers multiple parts, this is how we designate where the issue lives. (i.e. iOS and Android for cross-platform tablet app).

If the repository covers multiple parts, this is how we designate where the issue lives. (i.e. iOS and Android for cross-platform tablet app).

If the repository covers multiple parts, this is how we designate where the issue lives. (i.e. iOS and Android for cross-platform tablet app).

If the repository covers multiple parts, this is how we designate where the issue lives. (i.e. iOS and Android for cross-platform tablet app). Problems

Priority of a particular issue

Priority of a particular issue

Priority of a particular issue

Priority of a particular issue

Issues that make the product feel broken. High priority, especially if its present in production.

Issues that make the product feel broken. High priority, especially if its present in production.

Taking action, but need a few things to happen first. A feature that needs dependencies merged, or a bug that needs further data.