Releases: mireklzicar/issue-duration
Releases · mireklzicar/issue-duration
v0.0.3
What's Changed
- Updated thresholds and added thresholded_update feature by @mireklzicar in #1
- Changed default thresholds: 3, 10 to 7, 30 days
- Thresholded update allows to decrease the amount of relabeling (not every day but only if threshold is met)
Full Changelog: v0.0.2...v0.0.3
Fixed urgent bugs & added documentation
v0.0.2 npm build
v0.0.1
Issue Duration Labeler v0.0.1.beta
Introducting the first release of the Issue Duration Labeler action!
Features
- Automatically labels issues with their duration
- Color-codes labels based on configurable thresholds
- Works with both open and closed issues
- Customizable duration thresholds and label colors
- Runs on a schedule or can be triggered manually
What it does
This action scans all issues in your repository and adds a color-coded duration label to each. The duration is calculated as follows:
- For open issues: from creation date to current date
- For closed issues: from creation date to closed date
Labels are color-coded based on configurable thresholds:
- Short duration (default: ≤3 days): Green
- Medium duration (default: 4-10 days): Orange
- Long duration (default: >10 days): Red
Why use it?
- Quickly visualize the age of issues in your repository
- Identify long-standing issues that may need attention
- Track the lifecycle of issues more effectively
- Improve project management and team responsiveness