You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
In the scenario where:
Technical debt is accepted
The debt is partially solved (the measurement value improves)
New debt occurs
It is difficult to see that part of the technical debt is new and not consciously accepted.
Describe the solution you'd like
In step 2 above, the technical debt should automatically be changed to the current measurement value so that new technical debt is detected by Quality-time and the measurement status becomes red.
Describe alternatives you've considered
Manual administration
Additional context
This dynamic adaption of the technical debt target should be configurable on a metric-by-metric basis.
Automatic changes made by Quality-time to the technical debt value should be visible in the changelog of the metric.
Out of scope
Dynamically adapting the target and near target values when a measurement improves.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
In the scenario where:
It is difficult to see that part of the technical debt is new and not consciously accepted.
Describe the solution you'd like
In step 2 above, the technical debt should automatically be changed to the current measurement value so that new technical debt is detected by Quality-time and the measurement status becomes red.
Describe alternatives you've considered
Manual administration
Additional context
This dynamic adaption of the technical debt target should be configurable on a metric-by-metric basis.
Automatic changes made by Quality-time to the technical debt value should be visible in the changelog of the metric.
Out of scope
Dynamically adapting the target and near target values when a measurement improves.
The text was updated successfully, but these errors were encountered: