Overview
The Jira connector enables Hoopla customers to pull data from their Atlassian Jira Cloud instance for use in metric mapping, newsflashes, and user sync. It supports OAuth2 authentication and runs through Hoopla's pluggable connector framework.
Features
Supported
- OAuth2 authentication via Atlassian
- Metric mapping — count, sum, and average aggregations on issue data
- Filters on issue attributes: assignee, reporter, creator, project, status, issue type, priority, created/updated/resolution/due dates, time estimates, time spent, story points
- Newsflash triggers — fire a newsflash when issues match a configured filter
- Team sync — sync Jira projects into Hoopla as teams, with assigned users synced as team members (plus on-demand sync when an assignee surfaces in a metric/newsflash result) for metric attribution and leaderboards
- Time-range filters — built-in timespans (today, yesterday, this week/month/quarter/year, last week/month/quarter)
Not yet supported
- Cycle time (per-ticket date-difference calculations)
- Reopened tickets (requires Jira changelog API)
- Sprint filters (no sprint in openSprints() JQL support)
- Worklog entity
Setup
Customer enables the integration
The Jira connector is hidden behind a feature flag. Enable it for the customer by setting the tag from ex support site.
Customer authorizes via OAuth
From the Hoopla Integrations settings page:
- Customer clicks the Jira tile
- Redirected to Atlassian OAuth consent screen
- Selects the Jira site to authorize
- Returns to Hoopla — connector is created with authorized_by showing the authenticating user's name
Customer sync JIRA project as teams
Customer will need to select a project they would be synced into Hoopla as Hoopla teams.
Customer creates a dataset
After a JIRA team is synced into Hoopla, customer can now create a dataset for Metric Mapping. The dataset defines which entity to query (e.g. issue) and any base filters that apply across all mappings derived from it.
From the Integrations → Jira → Datasets page:
- Click New Dataset
- Enter a name (e.g. "All Open Bugs")
- Select the issue entity
- (Optional) Add base filters that scope every mapping using this dataset
- Save
Project field is mandatory. Customer will need to select the same project as the team they just synced.
Customer creates a metric mapping
From the Metrics page:
- Choose Jira as the data source
- Select an existing Jira dataset (created in step 4)
- Configure key attribute (e.g. assignee), value attribute (e.g. story_points), and aggregation type
- Add filters (e.g. status = "Done", created in this_month)
- Save — the mapping runs on the configured sync interval
Once Metric mapping is setup, Jira connector will automatically sync Jira users into Hoopla.
Customer creates a newsflash mapping
In order for Newsflash to work, customer will need to create a separate dataset just for newsflash. e.g. Create a dataset with Project = ‘Some Project’ and status = ‘In Progress’, which will create a newsflash that tracks issues updated since the previous sync. (On the first run it baselines against the last 365 days; after that it only picks up issues changed since the last successful run.)
Map Metrics to Hoopla channels
Go to channels page, configure your channel with Jira metric by adding leaderboards, newsflashes, etc.