actions-marketplace-validations/Jira Fields as PR Labels

Add labels to a pull request based on certain fields from Jira

View on GitHub

Trust Signals

Scorecard Score
not yet scored
Maintenance Recency
Stale
License
None
Runtime
Deprecated runtime
namedescriptionrequireddefault
github-tokenToken used to add labels to the PR. Can be passed in using {{ secrets.GITHUB_TOKEN }}yes
jira-api-tokenAPI Token used to access the Jira REST API. Must have read access to your Jira projects & issues. For details, see Atlassian's official documentation: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/yes
jira-usernameUsername that can use the Jira API token. Must have read access to your Jira projects & issues. For details, see Atlassian's official documentation: https://support.atlassian.com/atlassian-account/docs/manage-api-tokens-for-your-atlassian-account/yes
jira-base-urlYour Jira subdomain. i.e.: https://your-domain.atlassian.netyes
issue-key-locationWhere in the PR to look for issue key. Values can be: `branch`, `title` or `both`notitle
inject-jira-info-tableFlag indicating if the table with the basic ticket information should be added to the top of the PR descriptionnotrue
sync-issue-typeFlag indicating if the "issue type" from Jira should be added as a PR labelnofalse
sync-issue-priorityFlag indicating if the "priority" value from Jira should be added as a PR labelnofalse
sync-issue-labelsFlag indicating if the "labels" from Jira should be added as a PR labelnofalse
sync-issue-fix-versionsFlag indicating if the "fix versions" from Jira should be added as a PR labelnofalse
namedescription
issue-keyThe issue key that was found
issue-typeThe Jira issue type for the corresponding Jira issue
issue-priorityThe priority set in Jira for the corresponding Jira issue
issue-labelsThe labels set in Jira for the corresponding Jira issue
issue-fix-versionsThe fix versions on the corresponding Jira issue