Skip to content
Notis

Count unique on-chain entities from Jira updates

Turn an issue update into a clear count of distinct wallets or other queryable values.

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

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.

Why this helps

Teams can struggle to summarize how many unique entities appear in a blockchain dataset without building an aggregation by hand.

  • Summarize unique values with a purpose-built metric.
  • Reduce manual counting across query results.
  • Recalculate relevant counts after issue changes.

Setup

Build it in a few focused steps.

  • 1Connect Jira and Bitquery once in the Notis portal.
  • 2Create an automation and tell Notis which unique values to count and why.
  • 3Pick the Jira Updated Issue trigger for your project.
  • 4Choose a report destination and test against one real issue update with a known query context.

Questions about this workflow

Is the count exact?

Bitquery's Count Distinct Metric is for counting unique values. If you need an estimated unique count, specify that and use the Uniq Metric instead.

What should I tell Notis to count?

Name the data and dimension you want counted, such as unique wallets in a specified network and dataset. Bitquery schema details must be available or discoverable for the requested query.

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.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

Archive Database Query

Tool to query the archive database. use when you need full historical blockchain data (delayed by tens of minutes to hours).

ActionInstant

New Issue

Fires when a new issue is created in the Jira project you configure. Only issues created in that project produce an event.

TriggerInstant

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.

ActionInstant

New Project

Triggered when a new project is added in Jira

TriggerInstant

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.

ActionInstant

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.

TriggerInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.

ActionInstant

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.