Loading users...

Search Issues

Search for issues by title, key, or description

Component Showcase

Visual reference for all UI components used in the issue tracking system.

Issue Priorities

Priority levels indicate the urgency and importance of an issue.

LOW
NORMAL
HIGH
URGENT
Issue Types

Ticket types categorize the nature and purpose of an issue. Each type has a unique icon.

BugBUG
FeatureFEATURE
ImprovementIMPROVEMENT
TaskTASK
IncidentINCIDENT
Support RequestSUPPORT_REQUEST
DocumentationDOCUMENTATION
SpikeSPIKE
EpicEPIC
Sub TaskSUB_TASK
TestTEST

Icon Only Variant:

BUG
FEATURE
IMPROVEMENT
TASK
INCIDENT
SUPPORT_REQUEST
DOCUMENTATION
SPIKE
EPIC
SUB_TASK
TEST
Issue Statuses

Status indicates where an issue is in its lifecycle.

NewNEW
ConfirmedCONFIRMED
In ProgressIN_PROGRESS
ResolvedRESOLVED
ClosedCLOSED
ReopenedREOPENED
Version Statuses

Version status badges indicate the release state of a version.

WIPWIP
ReleasedReleased
LatestLatest
UpcomingUpcoming
Version Names

Version names are displayed with semi-bold text, underline, and status icons indicating WIP or Released status.

Projects

Projects are displayed with their name and key identifier. The key is shown in a monospace font.

Alternative Display Styles:

Project NamePROJ
Project NameDEVELOPER
PROJ
Users

User avatars display initials when no profile image is available.

A
Alice JohnsonReporter
B
Bob SmithDeveloper
C
Charlie BrownManager
D
Diana PrinceAdmin

Avatar Sizes:

S
Small User
D
Default User
L
Large User
Project Roles

Project roles define the permissions and responsibilities of users within a project.

ReporterREPORTER

Can create and view issues

DeveloperDEVELOPER

Can work on assigned issues

ManagerMANAGER

Can manage project settings and members

AdminADMIN

Full project access and administration

Complexity Levels

Complexity levels indicate how complex an issue is to implement, from simple to very complex.

Level 1
Level 2
Level 3
Level 4
Level 5

With Outlier Indicator:

Confidence Levels

Confidence levels indicate how confident an estimator is in their estimate, from very low to very high.

Level 1
Level 2
Level 3
Level 4
Level 5

With Outlier Indicator:

Priority Levels

Priority levels indicate the urgency and importance of an issue, from low to urgent.

LOW
NORMAL
HIGH
URGENT
Issue Resolutions

Resolution types indicate how an issue was resolved or closed.

Fixed
FIXED
Done
DONE
Duplicate
DUPLICATE
Won't Fix
WONT_FIX
Invalid
INVALID
Cannot Reproduce
CANNOT_REPRODUCE
Works as Designed
WORKS_AS_DESIGNED
Obsolete
OBSOLETE
Deferred
DEFERRED
Rejected
REJECTED

Icon Only Variant:

FIXED
DONE
DUPLICATE
WONT_FIX
INVALID
CANNOT_REPRODUCE
WORKS_AS_DESIGNED
OBSOLETE
DEFERRED
REJECTED
Tags

Tags help categorize and organize issues with flexible labels.

frontendbackendapidatabasesecurityperformanceui/uxtesting
Feature Maturity Levels

Maturity levels track the development stage of features from prototype to lovable.

PrototypePROTOTYPE
MinimalMINIMAL
ViableVIABLE
CompleteCOMPLETE
LovableLOVABLE

Maturity Progression:

Prototype
Minimal
Viable
Complete
Lovable
Feature Groups

Feature groups organize related features together. Each feature has a maturity level.

Authentication

User authentication and authorization features

OAuth LoginComplete
Two-Factor AuthenticationViable
Biometric LoginPrototype
Payment Processing

Payment and billing related features

Credit Card PaymentsComplete
Subscription ManagementViable
Invoice GenerationMinimal
User Experience

UI/UX improvements and enhancements

Dark ModeLovable
Mobile Responsive DesignComplete
Accessibility FeaturesViable
Issue Reactions

Users can react to issues with emojis. Reactions show vote counts and highlight the user's current vote.

With votes (user voted 👍):

Multiple reactions (user voted ❤️):

No votes yet:

Issue Relations

Issue relations link issues together to track dependencies, duplicates, and other relationships. Each relation type has a distinct icon and color scheme, styled like Issue Resolutions but with colored borders on both sides.

Relation Type Badges:

Duplicate
DUPLICATE
Depends On
DEPENDS_ON
Blocks
BLOCKS
Relates To
RELATES_TO
Clones
CLONES

Icon Only Variant:

DUPLICATE
DEPENDS_ON
BLOCKS
RELATES_TO
CLONES

Example Relations with Full Context:

PROJ-123Fix authentication bugIn Progress
Bug
Depends On
PROJ-456Implement user login featureResolved
Feature
Blocks
PROJ-789Similar issue reported earlierClosed
Bug
Duplicate
PROJ-101Related enhancement requestNew
Improvement
Relates To
PROJ-202Copy of original issueConfirmed
Task
Clones