Skip to content

Sync Security Hub findings and Jira issues #550

Sync Security Hub findings and Jira issues

Sync Security Hub findings and Jira issues #550

Triggered via schedule August 22, 2024 01:50
Status Success
Total duration 23s
Artifacts

sechub-jira-sync.yml

on: schedule
Run sync
9s
Run sync
Fit to window
Zoom out
Zoom in

Annotations

2 warnings
Run sync
The following actions use a deprecated Node.js version and will be forced to run on node20: aws-actions/configure-aws-credentials@v2. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
Run sync
Unexpected input(s) 'jira-host', valid inputs are ['jira-base-uri', 'jira-username', 'jira-token', 'jira-project-key', 'jira-ignore-statuses', 'jira-assignee', 'jira-transition-map', 'jira-custom-fields', 'aws-region', 'aws-severities', 'auto-close', 'dry-run', 'jira-link-id', 'jira-link-type', 'jira-link-direction', 'include-all-products', 'skip-products', 'jira-labels-config']