Planning eazyBI accounts is crucial for larger organizations.
There are no technical limitations on how many issues you could have per account and it could vary a lot depending on usage. Generally we suggest not to exceed 100K issues per account as this can influence report performance.
You might see performance issues for even smaller accounts if you use a lot of custom calculations in your account.
To maintain an optimal performance, please consider splitting your accounts by purpose, project, team, country, or any other meaningful way.
General accounts
Many issues, low granularity.
The data in a General account could be used for general overview, general KPIs, and trends where you do not need details. You can compare projects, teams, timeframes, etc.
Be aware that reports on issue level could lead to timeouts. To prevent this, you can use Data access roles to disable “drill into issues” action. Define a user role and set the bottom level at the Project level for all Issue hierarchies.
Import all projects or projects with a particular category, add JQL query for limiting data by time. Limit custom fields in account. Avoid issue change history import if possible. Use default stored measures for reports.
Use precalculated custom fields with JavaScripts instead of complex MDX formulas.
Team & Project Accounts
Accounts for teams and projects. Meant for daily usage, regular data imports several times per day, more details, custom fields, issue change history. Reports on detailed - issue levels.
Limit to one project or a small set of projects. Consider adding JQL to import actual issues for one team only.
These project accounts would work faster with small set of issues. However, they could share common reports/measures with other teams and projects. To do that you can use a common Template account for all your Teams so that each report could be replicated in all Team/Project accounts as needed.
Template accounts
Template accounts a accounts containing verified reports and measure sets. Use folders to organize your template reports. Consider using naming conventions, or glossaries.
It’s recommended to always use annotations for calculated measures.
Create your naming conventions in a way that template reports and measures do not interfere with reports and measures in team accounts.
Use report export definition and import definition to copy-paste reports from the template account to the team account.
Data access roles
Data access roles is an advanced account access management feature available in eazyBI.
You can define granular access roles for Jira users to prevent access to data, reports, dashboards, measures, etc.
Be aware that data access roles increase the overal complexity of eazyBI and and could lead to confusion. Plan these roles very carefully. Keep them as simple as possible.