insidewhy/action-jira-story-point-charts
Generate story point charts from jira issues and post them to slack
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Aug 3, 2025
- License
- MIT
Pinned Snippet
uses: insidewhy/action-jira-story-point-charts@fd89ed1a3fb399dc234783be8e6021dfa57b745c # v2.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| slack-channel | channel id of slack channel to post to | yes | — |
| charts | The charts to generate | — | — |
| story-point-estimate | Story point estimate to assign to issues with unset story points | — | — |
| jira-user | Jira user that created the auth token | yes | — |
| jira-base-url | Base URL of jira instance to retrieve data from | yes | — |
| jira-token | Jira auth token | yes | — |
| slack-token | Slack bot token | yes | — |
| jira-fields | Customise jira fields used for story points and times | — | — |
| jira-statuses | Customise jira statuses | — | — |
| jql | The jql used to select issues for the charts | — | — |
| summary | A summary text message to include with the charts | — | — |
| with-weekly-description | Add a textual summary of changes for this week with the given heading | — | — |
| with-daily-description | Add a textual summary of changes for this day with the given heading | — | — |
| store-work-item-history | Read and store work item history from/to the file system, this is required for the weekly-work-item-changes and daily-work-item-changes charts and also enhances the descriptions provided by with-weekly-description and with-daily-description | — | — |
| work-days | Work days for company as numbers from 0 (Sunday) to 6 (Saturday), defaults to 12345 | — | — |
Outputs
no outputs