actions-marketplace-validations/JIRA Wizard
Manage JIRA issues from Github and create releases out of it
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| app | The application to release and to set as component in the JIRA issues. | yes | — |
| host | The JIRA host | yes | — |
| The email to authenticate with the Jira and Confluence APIs | yes | — | |
| apiToken | The API token related to the email account to interact with Atlassian APIs | yes | — |
| projectKey | The JIRA project key that will reference the pushed release and the given issues. It will be used to detect JIRA issues with [KEY-*] format in the current context. | yes | — |
| issues | The JSON formatted list of JIRA issues that belong to the release. If none given, the action will try to find JIRA issues from the context based on the given issueRegex (or its default). | no | [] |
| issueRegex | The RegExp pattern to be matched globally for JIRA issues in the given context. If none given, it will automatically search for tasks with `\\[${projectKey}-\\d+\\]` format. | no | — |
| transitionId | The transition target of the JIRA issues. | no | — |
| version | The JIRA version to create, related to the given issues | no | — |
| draft | True if JIRA version is unpublished | no | true |
Outputs
no outputs