Keep creative context current on Jira issues
Refresh tracked work with current asset context so Jira remains a useful place to understand the state of delivery.
Trigger
Recurring schedule
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
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
Issue descriptions drift out of date when asset details or delivery context change after a task is first created.
- Keep Jira details aligned with available current asset context
- Reduce manual issue description upkeep
- Make important creative references easier to find
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 which existing Jira issues to refresh and how to update them with the current asset context it can access.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real Jira issue and its current asset context.
Questions about this workflow
How does the automation know which Jira issues to refresh?
Specify how to find them using information available to Notis, such as supplied issue keys or accessible issue data.
What if the current asset context is unavailable?
Notis cannot invent it. Supply the context or ensure it is available to the automation before the scheduled run.
Will this overwrite unrelated issue details?
Instruct Notis to update only the intended details and test on one real issue before relying on the recurring run.
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.