Configure Threshold of Failure/Warning per project from GUI
- Dominant language
- Java
- Stars
- 80
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
# Configure Threshold of Failure/Warning per project from GUI
## Context
For the moment, the Failure/Warning threshold of a project are configured in one of the json of a run.
If a project use a CI/CD for running ARA analysis and needs to increase its threshold, it can be quite painful to do.
## Expected
What would be more user-friendly is to configure thresholds in the GUI (of the cycles and/or of the project), instead of provided in a JSON for each execution.
Then, quality-thresholds would be saved to the execution while indexing to "remember how the thresholds were configured at the time the execution ran" and continue like now.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the existing JSON threshold configuration and the GUI flows for projects and cycles. Determine how thresholds should be stored and copied to an execution during indexing; done means users can configure both requested scopes in the GUI and executions retain the thresholds used when they ran.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100