Search for issues by title, key, or description
Impact describes how noticeable a change is for users and the product. It serves as a proxy for business value without requiring explicit ROI calculations or KPI metrics.
Description: Changes that are barely noticeable to users.
Use case: Minor bug fixes, internal refactoring, or improvements that only affect edge cases or have minimal user-facing impact.
Description: Small improvements that are noticeable but don't significantly change the product experience.
Use case: UI tweaks, small feature additions, or bug fixes that improve specific workflows without changing the overall product feel.
Description: Changes that are clearly noticeable to many users and improve the product experience.
Use case: New features, significant UI improvements, or enhancements that users will actively notice and appreciate.
Description: Major changes that significantly transform how users interact with the product.
Use case: Major feature releases, architectural changes, or improvements that fundamentally change the product experience or open new use cases.
Impact describes how strongly the product will feel different after implementing this change. It focuses on the spürbarkeit (perceptibility) of the change, not on type, effort, or priority.
This field serves as a proxy for business value without requiring explicit value assessments or ROI calculations. It helps teams understand the user-facing significance of their work.
Impact is an optional field with no default value. A conscious selection is required when setting impact.
The field can be left empty (null) if the impact is not yet determined or not applicable.
Icon Display:
Badge Display: