Refresh Jira context as market conditions change
Give selected Jira issues a recurring check against market developments, with updates only when the news changes the context your team uses.
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
Long-running work can retain assumptions that were reasonable when it started but no longer reflect current market conditions.
- Revisit assumptions on long-running work
- Keep meaningful changes recorded in Jira
- Avoid unnecessary edits when no new context matters
Setup
Build it in a few focused steps.
- 1Connect Benzinga and Jira once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3Tell Notis which Benzinga developments and Jira issues to review, what constitutes a material change, and how to update the issue while preserving existing details.
- 4Pick a recurring schedule and choose where run reports should go.
- 5Test with one real example and review the issue update.
Questions about this workflow
Does this workflow provide historical market baselines?
No. Notis can assess returned information, but a historical baseline must be supplied if the comparison depends on one.
Will the issue be edited every time the schedule runs?
Your instruction can limit updates to cases where the supplied news meets your material-change criteria.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Benzinga to Jira. A trigger fires from one place; an action lands in another.
Benzinga 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.
Benzinga 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.