Keep regression reports visible in Bugherd
Give regression reports a clear Bugherd follow-up task as soon as they arrive in Jira.
Trigger
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Action
Create Task
Tool to add a new task in a project. use when you have the project id and full task details ready.
Why this helps
A reported regression can blend into a busy Jira backlog without a distinct follow-up space.
- Create a visible follow-up for regression reports.
- Carry available problem context forward.
- Spend less time scanning the issue backlog.
Setup
Build it in a few focused steps.
- 1Connect Jira and Bugherd once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel.
- 3In one instruction, ask Notis to create a Bugherd task for new Jira issues identified as regressions and include available evidence.
- 4Pick the Jira New Issue trigger for the project you want to watch.
- 5Choose a report channel and test with one real regression issue.
Questions about this workflow
How does Notis identify a regression?
Specify how regressions are represented in your Jira issue details. Notis can only use signals available in the event.
Can Notis determine what version introduced a regression?
Only if the relevant version information is available in the issue data or supplied in your instruction.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Bugherd. A trigger fires from one place; an action lands in another.
Jira triggers
Bugherd actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Guest to Project
Tool to add a guest (client) to a project. use when you want to add an existing client by id or invite a new client by email.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Member to Project
Tool to add a member to a project in bugherd. use when you need to add an existing user to a specific project.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Create Attachment
Tool to add a new attachment to a task using an existing url. use when you have project and task ids and the external file url ready.
New Project
Triggered when a new project is added in Jira
Create Column
Tool to create a new column in a project. use when you need to add a custom workflow column after identifying the project id.
Updated Issue
Fires when an existing issue is changed in the Jira project you configure — for example its status, assignee, or any other field on the issue is updated. Only issues in that project produce an event. It does not fire on comment activity: adding, editing, or deleting a comment on an issue will not produce an event from this trigger.
Create Comment
Tool to add a new comment to a task. use when you need to record discussion or feedback on an existing task.
Create Project
Tool to create a new project. use when you need to initialize a project after gathering its name and url. example: "create a new project named 'my website' with url 'http://www.example.com'."
Create Task
Tool to add a new task in a project. use when you have the project id and full task details ready.
Create Webhook
Tool to create a new webhook for real-time event notifications. use when you need to configure a callback endpoint for task or comment events. example: "create a webhook for 'task create' events to be sent to 'https://example.com/webhook'."
Connect any two apps with Notis in the middle.
Jira and Bugherd, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Bugherd.