EasyBI - Importing not issue related data

[Sergio Baltazar]

Hello team.
We need to create a report that contains information unrelated to issues, such as groups and members in JIRA Service Management.
The rows should include group, members, status, and last login. We've managed to do this in EasyBI, but only partially, as it only shows users who have participated in a ticket, not all group members.
Your help would be greatly appreciated.
Regards

[Lara Demir - Hipporello]

Hi Sergio,

You've hit a common wall with the default Jira import. Because eazyBI’s standard Jira cube is built around Issue history, it only "sees" users who are linked to an issue. If a group member hasn't participated in a ticket, they effectively don't exist in that cube.

To get the full list of groups and members (including status and last login), you have two main options:

1. The "Additional Data Import" (Recommended)
You can import user and group metadata directly from Jira's database or via the Jira REST API as a separate data source.

Source: Use the Jira REST API for User Search.

Mapping: Map the data to a new, dedicated Cube (e.g., a "Users & Groups" cube) instead of the "Issues" cube.

Result: This cube will contain every user in your system, regardless of their ticket activity.

2. Import as User Properties
If you want to keep this within your existing "Issues" cube, you can upload an Excel or CSV file containing your full list of users and groups.

Mapping: During the upload, map the email or username to the User dimension and select "Add as property".

Limitation: Even with this, the user might only show up in reports if you use a specific "calculated measure" to force-display members with zero issues.

3. Use an App Integration (if available)
If you use Assets (formerly Insight) in JSM, you can sync Jira Users into an Assets Schema. eazyBI has a native Assets import that allows you to report on all objects (users) and their attributes (groups, status, last login) much more easily than the standard Issue cube.

My recommendation: Go with Option 1. Setting up a small REST API import for users is the "cleanest" way to get real-time login and status data without cluttering your Issue cube with thousands of inactive users.

Would you like some help with the specific REST API URL or the mapping settings for that import?