Clear completed research requests from Jira
When a research ticket reaches its cleanup point, remove only the request IDs it identifies from the intended collection.
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
Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
Why this helps
Completed research entries can linger in collections, making it harder to tell which requests still need attention.
- Clear a selected set of completed request entries in one call.
- Use the Jira update as a timely cleanup signal.
- Keep the cleanup scope explicit through request IDs in the issue.
Setup
Build it in a few focused steps.
- 1Connect Jira and Asin data api once in the Notis portal.
- 2Create an automation in Automations, New Automation, and give it a clear name.
- 3In one instruction, ask Notis to clear only the request IDs explicitly listed in the updated issue from its identified collection when the issue indicates completion.
- 4Pick the Jira Updated Issue trigger and choose where run reports should go.
- 5Test with one real updated issue containing the target collection and request IDs.
Questions about this workflow
Will it clear every request in a collection?
The instruction should name only the request IDs to remove. The available action clears multiple requests by IDs; it is not a request to clear an entire collection.
What if the issue does not provide request IDs?
Notis needs the specific IDs to carry out a selective removal. If they are missing, the instruction should have Notis report that the cleanup details are incomplete.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Asin data api. A trigger fires from one place; an action lands in another.
Jira triggers
Asin data api actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Clear multiple collection requests
Tool to delete multiple requests from a collection by ids. use when you need to remove a selected set of request entries from an existing collection in a single call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List Collection Requests
Tool to list all requests in a collection (paginated). use when you need to paginate through requests for a specific 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.
New Project
Triggered when a new project is added in Jira
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.
Connect any two apps with Notis in the middle.
Jira and Asin data api, 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 Asin data api.