Jira Ticket Transitioner

This action can move Jira issue to col of choice by event (e.g: move to IN REVIEW col when author requests review, move to IN PROGRESS if reviewer requests changes, move to QA if pr is merged).

Inputs

• github-token

  • Required
  • Usually it can be found at ${{ secrets.GITHUB_TOKEN }}, see this link for more info

• column-to-move-to-when-review-requested

  • Required
  • Case-sensitive, status of an issue
  • If issue can not be moved or the status is not found, simply do nothing

• column-to-move-to-when-changes-requested

  • Required
  • Case-sensitive, status of an issue
  • If issue can not be moved or the status is not found, simply do nothing

• column-to-move-to-when-merged

  • Optional
  • Case-sensitive, status of an issue
  • If issue can not be moved or the status is not found or not provided, simply do nothing

• jira-endpoint:

  • Optional (required when not using @atlassian/gajira-login)
  • See Jira Rest API docs

• jira-account:

  • Optional (required when not using @atlassian/gajira-login)
  • See Using Jira API with Basic header scheme

• jira-token:

  • Optional (required when not using @atlassian/gajira-login)
  • See Using Jira API with Basic header scheme

• jira-issue-id:

  • Optional
  • Case-sensitive
  • Issue key, e.g: FOO-432, UMA-501, ...

Important

Although all jira-* (except for jira-issue-id) inputs are optional, they must be provided explicitly unless you are using @atlassian/gajira-login.

@atlassian/gajira-login is an action that will write jira config data to a temporary file during the workflow so that other action can extract from it rather than having to input data.

Starting from v1.0.5, the jira-isssue-id input will be optional due to the reason that some PRs are considered small enough and won't be linked to any Jira issue, therefore, it makes sense to exit safely without failing the workflow.

Example

# Use this and you won't have to provide `[jira-endpoint, jira-account, jira-token]` down there
- 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 }}


  ...
- uses: tuanddd/jira-automate-transition@v1.0.5
  with:
    github-token: ${{ secrets.GITHUB_TOKEN }}
    column-to-move-to-when-review-requested: In Review
    column-to-move-to-when-changes-requested: In Progress
    column-to-move-to-when-merged: QA
    jira-endpoint: https://...        # 3 inputs here are not required
    jira-account: example@mail.com    # if you use the action mentioned
    jira-token: ******                # above
    jira-issue-id: FOO-312