Keep Jira current when a creative brief changes
Reflect a changed asset format, delivery date, or brief in the Jira issue that tracks the work.
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 small change to a creative brief can leave Jira describing work the team is no longer expected to deliver.
- Keep Jira issue details aligned with an updated brief
- Carry forward the change context supplied with the request
- Make scope changes easier to spot and follow up
Setup
Build it in a few focused steps.
- 1Connect Abyssale and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a name.
- 3Tell Notis to update the identified Jira issue with the changed creative requirements and a concise note about what changed.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real brief change and its Jira issue key.
Questions about this workflow
What identifies the issue to update?
Include its Jira key or id in the webhook request.
Can it update only the changed details?
Tell Notis which supplied changes to apply. Jira's Edit Issue action supports field values and operations, and direct parameters take precedence over the fields parameter.
Will it know what changed from the earlier brief?
Only if the prior brief or a clear change summary is included in the request or available to Notis. Supply a baseline when needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Abyssale to Jira. A trigger fires from one place; an action lands in another.
Abyssale 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.
Abyssale 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.