Skip to content

research(OS_Scan): Research on how to handle component version in policy violation based scanners #989

research(OS_Scan): Research on how to handle component version in policy violation based scanners

research(OS_Scan): Research on how to handle component version in policy violation based scanners #989

name: Sync GitHub issues to Jira example
on: [issues]
concurrency:
group: sync-issues-to-jira-${{ github.event.issue.number }}
jobs:
sync-issues:
name: Sync issues to Jira
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: cloudoperators/sync-issues-github-jira@main
with:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
JIRA_URL: ${{ secrets.JIRA_URL }}
JIRA_USERNAME: ${{ secrets.JIRA_USERNAME }}
JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
JIRA_COMPONENT: ${{ secrets.JIRA_COMPONENT }}
JIRA_PROJECT_KEY: ${{ secrets.JIRA_PROJECT_KEY }}
JIRA_EPIC_KEY: ${{ secrets.JIRA_EPIC_KEY }}
JIRA_AUTHORIZATION: ${{ secrets.JIRA_AUTHORIZATION }}