Used to store credentials for later use by other Jira Actions
For examples on how to use this, check out the gajira-demo repository
This is required by other actions like:
Transition- Transition a Jira issueComment- Add a comment to a Jira issueCreate- Create a new Jira issueFind issue key- Search for an issue key in commit message, branch name, etc. This issue key is then saved and used by the next actions in the same workflowTODO- Create a Jira issue for each TODO comment in committed codeCLI- Wrapped go-jira CLI for common Jira actions
An example workflow to create a Jira issue for each //TODO in code:
on: push
name: Jira Example
jobs:
build:
runs-on: ubuntu-latest
name: Jira Example
steps:
- name: Login
uses: atlassian/gajira-login@master
env:
JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }}
JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
- name: Jira TODO
uses: atlassian/gajira-todo@master
with:
project: GA
issuetype: Task
description: Created automatically via GitHub Actions
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}More examples at gajira-demo repository
JIRA_BASE_URL- URL of Jira instance. Example:https://<yourdomain>.atlassian.netJIRA_API_TOKEN- Access Token for Authorization. Example:HXe8DGg1iJd2AopzyxkFB7F2(How To)JIRA_USER_EMAIL- email of the user for which Access Token was created for . Example:[email protected]
- None
email- user emailtoken- api tokenbaseUrl- URL for Jira instance
endpoint- URL for Jira instancelogin- user email
JIRA_API_TOKEN- Jira API token to use with CLI