actions-marketplace-validations/Jira Telegram
Link Jira tickets without compromising Pull Request Titles.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| github_token | Authorized github token to read and write to pull requests | yes | — |
| jira_host | Hostname for where your team's Jira instance is hosted | yes | https://jira.mycompany.com |
| project_keys | A comma separated list of project keys to be matched on in a pull request body. (E.g. https://jira.mycompany.com/browse/PROJ-123 - you'd list PROJ in this string | no | — |
| ignored_project_keys | A comma separated list of project keys to not be matched on in a pull request body. (E.g. https://jira.mycompany.com/browse/PROJ-123 - you'd list PROJ in this string | no | — |
| first_ticket_only | When true - only the first Jira ticket found will be committed to the Pull Request | no | — |
| use_pr_comment_blocks | When true - Jira Telegram will only pick up tickets inside of the telegram comment blocks | no | — |
Outputs
no outputs