Use Jira updates to start historical chain research
When an issue changes, ask Bitquery for the historical blockchain data needed to revisit the investigation.
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
Archive Database Query
Tool to query the archive database. use when you need full historical blockchain data (delayed by tens of minutes to hours).
Why this helps
New status or ownership changes can leave teams repeating historical research without seeing what the archive contains.
- Revisit older on-chain activity when issue details change.
- Use archived data suited to historical investigation.
- Keep the research run associated with an updated ticket.
Setup
Build it in a few focused steps.
- 1Connect Jira and Bitquery once in the Notis portal.
- 2Create an automation with one instruction describing the historical data to retrieve when an issue changes.
- 3Pick the Jira Updated Issue trigger for the project you use.
- 4Choose where run reports go, then test using one real issue update and a known historical reference.
Questions about this workflow
How current is archive data?
Bitquery's archive database can be delayed by tens of minutes to hours, so it is intended for historical queries rather than the freshest activity.
Which Jira changes can trigger this?
The event fires when an existing issue in the configured project is changed, such as its status, assignee, or another field. Comment activity does not fire this event.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Jira to Bitquery. A trigger fires from one place; an action lands in another.
Jira triggers
Bitquery actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Aliases Metric
Tool to use graphql aliases to rename fields in the response for clarity and disambiguation. use when you need to query multiple metrics with identical field names in one call.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Archive Database Query
Tool to query the archive database. use when you need full historical blockchain data (delayed by tens of minutes to hours).
New Issue
Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.
Combined Database Query
Tool to query the combined database, which merges archive and real-time databases. use when you need both historical and up-to-the-second blockchain data in one request.
New Project
Triggered when a new project is added in Jira
Conditional Metrics Snippet
Tool to generate a graphql metric snippet with conditional logic. use when you need to apply filters directly on metric calculations via the `if` attribute.
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.
Count Distinct Metric
Tool to use the count distinct metric to aggregate unique values for a field. use when you need to count the number of unique occurrences in a dataset.
Count Metric
Tool to use the count metric to aggregate the number of records matching a graphql query. use when you need simple record counts.
Database Selection
Tool to select the database (archive, realtime, combined) to query at the top level of a graphql request. use after determining whether you need live, historical, or combined blockchain data.
Early Access Program Query
Tool to access streaming data across various blockchain networks for evaluation purposes. use when querying chains not available via the v2 endpoint; limited to real-time data only.
Connect any two apps with Notis in the middle.
Jira and Bitquery, 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 Bitquery.