In the eazyBI plugin, you can create one or several accounts. One eazyBI account contains a set of imported Jira projects data which can be accessed by eazyBI account users (access to eazyBI accounts data is managed separately from Jira security schemes).
If you have few Jira projects and there is no need to limit access to eazyBI reports by different Jira user groups then you can use just one eazyBI account and import all Jira projects in this account.
If you have a large number of Jira projects and a large number of Jira issues then it is recommended to plan several eazyBI accounts and import related set of Jira projects and data in each eazyBI account. As each eazyBI account stores imported Jira data in separate database scheme tables then it could help also for eazyBI reports performance optimization.
In eazyBI you can create one or several eazyBI accounts.
In each eazyBI account, you can import a separate set of Jira projects and create a separate set of reports and dashboards that are needed for these Jira projects. You can grant access to this eazyBI account to selected Jira users and user groups. Please take into account that eazyBI account access should be defined separately from Jira security schemas.
Let's have a look at how you create and manage accounts in eazyBI.
You see the list of all eazyBI accounts that are available to you in the eazyBI Home tab.
You can navigate to account's reports or dashboards from the corresponding account section. In the browser URL, you can see an account ID number – you might need it, for example, when investigating some problems in eazyBI log files.
You also see the current eazyBI account name in the top right navigation bar. From this top navigation menu, you can quickly switch to a different account.
If you are a Jira administrator then you can create a new eazyBI account. You will be assigned as the owner for this new account. As an owner, you can edit which users and user groups have access to this account. You can navigate to account users page either from this All accounts page, from Home tab or from the top navigation bar Accounts menu.
When you have created a new account then only you can access it. You need to add which other individual users or user groups will have access to this account. When adding a new user or a user group you need to specify their role:
- Dashboard viewer can only view eazyBI dashboards in eazyBI Dashboards tab as well as view eazyBI gadgets on Jira dashboards.
- Viewer can view any report in the Analyze tab.
- User can also create their own reports but cannot modify reports created by others.
- Reports admin can manage reports by any user as well as create and update calculated members.
- Data admin can import new data sources from Source Data tab as well as do everything what "Reports admin" can do.
- User admin can access this page and add new users as well as do everything what "Data admin" can do.
If needed you can transfer eazyBI account ownership from this page to any other existing account user – change their role to Owner and confirm your action. Please note that you will not be able to undo this action.
If you are Jira System Administrator then from eazyBI top navigation System Administration menu you can access All users page. In this page, you can see all Jira users who have been using eazyBI and see all the accounts that they own or have access to. You can go to any eazyBI account from this page. Even if Jira System Administrator is not added to a particular eazyBI account they can open any eazyBI account and act with the same permissions as this account owner. It also means that Jira System Administrator can change any eazyBI account owner to a different one.
If you do not need anymore some account then you can delete it from All accounts page. Please take into account that it will delete all imported data as well as all created reports and dashboards in this account.
If you have a large number of Jira projects and issues then it is also recommended to use several eazyBI accounts and import in one account just set of related projects. Each eazyBI account uses a separate database schema and tables and therefore your reports will perform faster when using several smaller eazyBI accounts with smaller size database tables and not just one large eazyBI account with large size database tables.
If you have any other questions about eazyBI accounts then please let us know.
eazyBI stores imported Jira data in a multi-dimensional data cube. Cubes contain fact data that are divided by dimensions and each detailed fact “cell” contains measure values about that fact.
Below is an example of Issues cube that has Project, Priority and Time dimensions and has measures Issues created, Issues due and Issues resolved. Each detailed cube “cell” contains a number of issues created, due and resolved for a particular project, priority and time period.
It is easy to illustrate cube with three dimensions but in the real eazyBI issues data cube, you will have many more dimensions and many more measures which will be described below.
Each dimension has either just detailed level of all dimension members or has a hierarchy with several levels. For example, Project dimension has Project and Component levels.
All measures are automatically aggregated (typically as the sum of detailed level values) in upper hierarchy levels. If the issue can belong to several level members (e.g. issue can have several components) then measure value at the upper hierarchy level will not be the sum of detailed level measure values.
Typically each dimension has All level with one All member which aggregates all dimension members.
Time dimension will have two hierarchies - one with Year, Quarter, Month and Day levels and another Weekly hierarchy with Year, Week and Day levels. You can also add a custom hierarchy for Fiscal monthly and multiple weeks.
eazyBI stores imported data in a multidimensional data cube. We are used to two-dimensional tables with rows and columns - for example, spreadsheets.
But in the case of multidimensional cubes, there can be very many dimensions.
And the intersection of these dimensions there are data cells which store fact data and they are called Measures.
In this simple example, we are looking at the issues cube that has Project, Priority and Time dimensions.
It has measures issues created issues due and issues resolved.
Each detailed cube cell contains a number of issues created, due and resolved for a particular project, priority and time period. Each dimension has one or several hierarchies and each hierarchy also has several levels.
Each dimensional hierarchy level includes individual dimension members.
In the simplest case, for example, the Status dimension has just one hierarchy with the all level which includes a number All Statuses and a detailed status level which includes individual members for each status.
Each dimension always has the All member which aggregates all members of the dimension.
A hierarchy can also have more levels.
Let's take a look at the fixed version dimension example. In this case, there is All level, then a Project level which includes all versions for a particular project, then a status level with archived or released and unreleased numbers and then a detailed version level with individual members for a particular project and status versions.
A dimension can also have several hierarchies.
The standard Time dimension has a default hierarchy with Year, Quarter, Month and Day levels as well as a weekly hierarchy with a Year, Week and Day levels. You can also define an additional Fiscal hierarchy if your fiscal year starting month is not January. Please note that in one report you can use just one hierarchy for a particular dimension. For example, you can make either a monthly report with several latest months or a weekly report with several latest weeks.
Let's have a look at JIRA issues data cube Dimensions and hierarchies in eazyBI.
When you open Issues data cube in eazyBI Analyze tab then you'll see all available dimensions in this cube - both for standard Jira Issue fields as well as for selected custom fields. There are a special dimension Measures which includes all measures that are available in this data cube.
Let's select Issues created measure on columns. Now let's move Priority dimension to rows and by default, all priorities member is selected. In Priority dimension all hierarchy level members section we see all hierarchies and levels for this dimension.
In this simple case, there is just one Priority detail level. If we select that then in the results area we see the list of all detailed dimension members for each priority.
If we take a look at the Project dimension all hierarchy level members then we see that this dimension has one hierarchy with a project level and a component level.
Let's move the project dimension to pages and select all project level members. Now in pages selection, we see a list of all projects and we can expand each project to a detailed list of components as well.
Now we will move the Priority dimension to columns and the Time dimension to rows. For the Time dimension in all hierarchy level members, we see that there is a default hierarchy with a Year, Quarter, Month and Day levels as well as a weekly hierarchy with a year week and day levels. Now we can select for example or all month level members or all week level members as a result in the report we see a number of created issues in one selected project with particular priority and within the particular Time period.
The eazyBI will import Jira issue fields either as dimensions, measures or Issue dimension properties.
- Issue fields which are a list of value fields, like issue type, priority, version, label, status, resolution, assignee, the reporter are imported as eazyBI dimensions.
- Numeric fields like story points, estimated hours, remaining and spent hours will be imported as measures. And we can get the total of these numeric measures by other dimensions.
- Date fields like Issue created or resolved date, are also imported as measures we can get the total number of issues in the corresponding Time dimension period which includes this date.
Many show fields are also imported as Issue dimension properties.
You can use these properties when creating an eazyBI report with Issue dimension detailed members on rows and property measures and columns.
Please continue to read more about the standard measures and dimensions in the documentation pages.