levigo/jira-cve-action
Automatic issue creation for CVEs
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| jiraBaseUrl | Jira Cloud host URL | no | levigo-solutions.atlassian.net |
| jiraUser | Technical user to access jira with | yes | — |
| jiraUserToken | Technical users token to access jira with | yes | — |
| CVEResults | Results of a aquasecurity/trivy-action in JSON format | yes | — |
| projectKey | Your project in jira name | yes | — |
| parentIssue | Your CVE parent ticket key | no | — |
| versionTag | Version tag to use for the CVE issue | no | — |
| activeStatus | Status for tickets that can be fixed by updating the dependency | no | — |
| boardId | The ID of the Sprint board where the issue will be added to | no | — |
| issueType | Issue Type for the new Jira Ticket (e.g. Task or Sub-Task) | no | — |
| sprintFieldId | The field-ID (in Jira) that reflects the field Sprint (e.g. customfield_10020) | no | — |
| waitingStatus | Status for tickets that can not be fixed by updating the dependency | no | — |
| ref | The branch, tag or general identifier. Defaults to the github action context ref. | no | — |
| addScoreToTicket | If true, add CVSS score to the Jira ticket description | no | true |
| debug | If true, add additional log messages | no | false |
Outputs
no outputs