Refresh Jira issue details when BugHerd feedback changes
When a report changes, help the Jira issue reflect the latest useful information without another manual rewrite.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Edit Issue
Updates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields parameter. direct parameters take precedence.
Why this helps
A Jira ticket can become stale when a BugHerd report gains clarifications, screenshots, or updated details.
- Reduce repeated manual edits across feedback and issue tracking.
- Keep relevant new report details visible to the engineering team.
- Make it easier to act on clarifications after initial triage.
Setup
Build it in a few focused steps.
- 1Connect BugHerd and Jira once in the Notis portal.
- 2Create an automation from any channel or in Automations > New Automation.
- 3Describe how to find the related Jira issue and update only the relevant details from the BugHerd report.
- 4Choose the webhook trigger and a channel for run reports.
- 5Test with one updated report that has a known Jira issue reference.
Questions about this workflow
How does Notis know which Jira issue to update?
Include a Jira key or another reliable issue reference in the BugHerd data or automation instruction. If there is no reliable match, Notis may need to report that rather than guess.
Can it avoid overwriting unrelated Jira fields?
Instruct Notis to update only the relevant details supported by the report. Review the first run to confirm the result matches your team's expectations.
Will missing details be filled in automatically?
No. Notis can use details available in BugHerd and Jira. Any missing context or history must be supplied or retrieved.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Bugherd to Jira. A trigger fires from one place; an action lands in another.
Bugherd triggers
Jira actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Attachment
Uploads and attaches a file to a jira issue.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Comment
Adds a comment using atlassian document format (adf) for rich text to an existing jira issue.
Add Watcher to Issue
Adds a user to an issue's watcher list by account id.
Assign Issue
Assigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
Creates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Create Issue
Creates a new jira issue (e.g., bug, task, story) in a specified project.
Link Issues
Links two jira issues using a specified link type with optional comment.
Create Project
Creates a new jira project with required lead, template, and type configuration.
Connect any two apps with Notis in the middle.
Bugherd and Jira, 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 Jira.