atlassian / gajira

GitHub Actions for Jira
199 stars 23 forks source link

Login Action is logging in as `undefined` #12

Open anarian opened 3 years ago

anarian commented 3 years ago

I'm trying to set up actions to transition tickets when pull requests are opened/closed, but using the atlassian/gajira-login action is logging me in as undefined, causing the other actions to fail.

image

This is my current actions definition:

name: Transition ticket for PRs

on: pull_request

jobs:
  build:
    runs-on: ubuntu-latest
    name: Jira Ticket Transition
    steps:
    - name: Checkout repository
      uses: actions/checkout@v2

    - name: Login
      uses: atlassian/gajira-login@v2.0.0
      env:
        JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
        JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }}
        JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}

    - name: Find ticket IDs in commit messages
      uses: atlassian/gajira-find-issue-key@v2.0.2
      id: ticketids
      with:
        from: commits
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

    - name: Transition to "In Code Review"
      id: transition-incodereview
      if: ${{ github.event.pull_request.action == 'opened' }}
      uses: atlassian/gajira-transition@v2.0.2
      with:
        issue: ${{ steps.ticketids.outputs.issue }}
        transition: "In Code Review"
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

    - name: Transition to "Ready to Deploy"
      id: transition-readytodeploy
      if: ${{ github.event.pull_request.action == 'closed' && github.event.pull_request.merged == true }}
      uses: atlassian/gajira-transition@v2.0.2
      with:
        issue: ${{ steps.ticketids.outputs.issue }}
        transition: "Ready to Deploy"
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

Update: Also added a actions/checkout@v2 run before this, since it wouldn't have been able to get the git history to find the ticket IDs, but the authentication is still returning undefined and the error in gajira-find-issue-key is still the same.

dadamsGS commented 2 years ago

I am getting the same error. Any movement on this?

fahedyasin commented 2 years ago

I am getting the same. any updates?

GeDiez commented 2 years ago

same here, any solution around this?

dja557 commented 2 years ago

same here