Jira
A Jira task when the count crosses the line.
Connect Jira Cloud to a project. A rule watches an issue and opens one task for a team. The same episode does not open a second task.
What it does
Automation has three pieces. A project receives the errors. A team owns a Jira project key, an issue type, and optional labels. A rule says how many events, inside a window, should file one task for that team. The windows are 15 minutes, 1 hour, 6 hours, and 24 hours.
The task description includes the issue title, the count inside the window, the total events, the latest release when one was sent, the file, and a link back to the issue. The issue page stores the Jira key and URL.
Business and Test create the Slack message and the Jira task when a rule is crossed. On Base the connection can be saved, and a burst does not send it. Slack is a separate incoming webhook on the same project. A task is created only when Jira is connected.
Connect Jira Cloud
- Create a project and copy its key from the project page.
- Open Automation. Slack and Jira are saved per project.
- Enter the Jira site URL, such as https://your-team.atlassian.net, the Atlassian account email, and an API token. The token is stored encrypted. Leave the token field blank later if you only want to keep the saved one.
- Add a team with the Jira project key, the issue type (Bug is the default), and any labels.
- Add a rule: a name, one project or all projects, the team, the event count, and the window. "Open a new task if it regresses" is on by default.
There is no marketplace app to install. TraceHawk calls Jira with the token you paste.
When a second task is created
The first time a rule crosses its count, one task is filed. Further events on that issue do not file another task for that rule. If you resolve the issue and the same stack comes back, TraceHawk marks the issue regressed. When the rule still has "Open a new task if it regresses" checked, that regression can open another task. If the box is off, resolving the issue does not arm a new task.
Supported features
- Jira Cloud, using the site URL, email, and API token.
- Project key, issue type, and labels on the team.
- A rule for one project or every project.
- Thresholds in 15 minutes, 1 hour, 6 hours, or 24 hours.
- One task per episode, then another only after a regression if you asked for that.
- A Slack webhook on the same project, sent on Business and Test when the rule crosses the line.
Troubleshooting
- The workspace is on Base. The connection saves, and the burst does not create a task. Business and Test send it.
- Jira is only half filled in. The site URL, email, and API token are all required before a task can be created.
- The team project key does not match a project in that Jira site, or the issue type name does not exist there.
- The count inside the window has not reached the rule. Total events on the issue are not the same number as events inside the window.
- A task already exists for this episode. Resolve the issue, let it regress, and leave the regression checkbox on if you want another task.
- Do not email the API token. The Automation page is where it is replaced.
Questions
Does every error open a Jira issue?
No. A rule opens one task after the number of events you set, inside 15 minutes, an hour, 6 hours, or a day. Until that count is crossed, the TraceHawk issue exists and Jira is quiet.
Which plans create the task?
Business and Test. Base can store the Jira connection and the Slack webhook, and a burst does not send them.
Will the same bug open a task on every event?
No. One task is filed for the episode. Another task waits until the issue is resolved, comes back, and the rule is set to open a task on regression.
Is this a Jira Marketplace app?
No. You paste the Jira Cloud site URL, the account email, and an API token on the Automation page. The token is encrypted before it is stored.