How to bypass Github Copilot authentication errors within a workflow transition?

[Martin HADOBAS]

I have assigned Github Copilot to specific transitions on my Jira board (Development, Code Review, etc.)

However, whenever I change the status of a ticket, the Github Copilot agent triggers, but cannot authenticate. Instead, I have to manually click on the Agents tab, select Github Copilot, and then it authenticates with my personal user account. However, this way I cannot set up a custom prompt, the agent just starts working.

I want to set up a way to have Agentic Development workflow, with Github Copilot writing the code and creating a PR when a ticket is moved to Development, for the agent to review the PR when the ticket is moved to Code Review, etc. However, since the agent doesn't authenticate with a user account in these transitions, I just get an Authentication error.

How can I fix this? It seems like there is a good opportunity for having this workflow with Github Copilot, but I cannot get it to work due to these authentication issues.

[Viswanathan Ramachandran]

Hi @Martin HADOBAS 

TL;DR: The authentication error happens because Jira status transitions run as background system tasks, which cannot invoke interactive personal OAuth sessions.

To get this working 

• Switch from User OAuth to Service Credentials:  Configure a Fine-grained Personal Access Token (PAT) with the right access. This allows background tasks to authenticate without needing individual user logins.

• Use Jira Automation instead of Transition Triggers: Instead of linking Copilot directly inside the workflow transition settings, create rules under Project Settings - Automation.

• Add Custom Prompts: Use the Issue Transitioned trigger then add the Copilot action. This lets you pass ticket context and custom system prompts for automated code generation or PR reviews.

If it helps https://community.atlassian.com/forums/Jira-articles/New-Put-your-coding-agents-to-work-with-Jira-Automation/ba-p/3268918