Check publication history when Jira work changes
Bring past Curated issues into view when a Jira change may affect planned coverage.
Trigger
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.
Action
List Issues
Tool to list all issues for a publication. use after you have the publication id and need to fetch its issues (supports pagination).
Why this helps
Changed plans can create overlapping newsletter work when earlier issues are out of sight.
- Retrieve publication issues for reference.
- Make editorial overlap checks easier.
- Keep a link between project changes and publication planning.
Setup
Build it in a few focused steps.
- 1Connect Jira and Curated once in the Notis portal.
- 2Create an automation for editorial history checks.
- 3Tell Notis to list issues for the confirmed Curated publication after relevant Jira issue updates.
- 4Pick the Jira Updated Issue trigger and choose a report channel.
- 5Confirm the publication id and test with one real update.
Questions about this workflow
Does the action identify duplicate topics?
It lists publication issues. Notis can compare returned information with the Jira update when that information is available.
Can it see every Curated issue?
The list action supports pagination, so ask Notis to account for pages when a full history is needed.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Curated. A trigger fires from one place; an action lands in another.
Jira triggers
Curated actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Draft Issue
Tool to create a draft issue for a publication. use after confirming the publication id. applies default settings if optional fields are omitted.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Collected Link
Tool to create a collected link for a publication. use when you want to add a new link (with url, title, etc.) to a publication's collection.
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
List Email Subscribers
Tool to list all email subscribers for a publication. use after confirming the publication id.
New Project
Triggered when a new project is added in Jira
List Publications
Tool to list all publications accessible by the api key. use when you need to retrieve your publication ids for further api calls. example prompt: "list my publications".
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.
List Categories
Tool to list all categories for a publication. use after you have the publication id and need to fetch its categories.
List Issues
Tool to list all issues for a publication. use after you have the publication id and need to fetch its issues (supports pagination).
Connect any two apps with Notis in the middle.
Jira and Curated, 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 Curated.