jenkinsci / jenkinsci/lockable-resources-plugin
UX: better wording for queued filter
- Dominant language
- Java
- Stars
- 99
- Forks
- 205
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 8
Description
> Hello,
>
> The "Queued" option in the Resources tab filter filters resources that are requested by freestyle jobs waiting in the build queue, but the label doesn't make that clear.
> Pipeline lock() waits don't mark the resource, so on a pipeline-only controller this filter will always return zero results.
> Could the label be changed to indicate the freestyle case (for example, "Required by freestyle")?
_Originally posted by @kohtaro-satoh in [#1040](https://github.com/jenkinsci/lockable-resources-plugin/issues/1040#issuecomment-5098276828)_
Contributor guide
Research direction
No file or test is named. Start at the Resources tab's filter implementation and trace the "Queued" label. Done means the label clearly indicates that it applies to resources requested by queued freestyle jobs, while preserving the existing filter behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100