Jira

With Jira connected the agent turns a bug report into a Jira issue with a clear summary, the details and the visitor's email for follow-up, and tells the visitor the issue key.

What the agent can do

There is deliberately no "check issue status" action: issue trackers are for your team, not your customers.

Connect Jira

1. Create an API token

   Go to id.atlassian.com/manage-profile/security/api-tokens → Create API token, name it PepoChat, pick an expiry (up to one year) → Create → Copy. If Atlassian asks about scopes, create it without scopes or with write:jira-work.

2. Enter the account email

   Use the email of the Atlassian account that created the token; Jira checks the pair, and issues show that account as the reporter.

3. Site and project

   Your Jira site is your Atlassian address, for example yourcompany.atlassian.net. The project key is the prefix of that project's issue numbers (SUP for SUP-123). The project must have the Task issue type; company-managed and team-managed software projects do by default, Jira Service Management projects usually do not.

4. Add, test, enable

   Under App Integrations → Jira, fill in the four fields, click Add actions, test with a sample bug, then enable. Delete the test issue in Jira.

Example

Visitor: The CSV export button does nothing on Safari.

Agent: Thanks, I've filed that with engineering as SUP-42 with your details. We'll follow up by email when it is fixed.

Good to know

• Tokens expire on the date you chose. Put it in your calendar; when it comes, delete the Jira action and add it again with the new token.
• "Specify a valid issue type" means the project has no Task type.