Importing data from 3rd Party with custom dimensions

Hi.

We use Jira extensively as our work tracking software. We have a 3rd party plug in called “productive.io” which is used to track time entries. This 3rd part system has an understanding of Customer, Project, Budget etc. and its possible to record time directly in that platform if you are not working on a Jira related Ticket.

We have used EazyBI and set up a Rest API import to import Time Entries.. you can see the hierarchy on this page API Documentation. As part of the mapping we can make a Jira Issue to a time Entry and so that allows us to map to Measure of the issue. You can see the mapping below… In some instances we have time recorded which is not related to an issue, but is related to a Service ( a service is kinda like an overall budget/maybe a project, but isnt directly related to a Jira Project. )

What im trying to do is Import ALL of these time sheet entries. I want to be able to report by Service.. and see time which both map to a Jira issue and Time which doesnt map to a jira issue. Therefore for a service i could see the break down of Jira Related work and non jira related work. I cant figure out the best approach for this. Technically there is a Budget service i could call in Productive, but a budget maps to a service so i need to solve this first step. Im looking for guidance on the bet way to do this, it seems like it should be a common pattern and id like to report by service to see the list of issues etc.. and hours logged in jira and outside of jira. Im clearly missing something as it feels a basic thing for me to solve yet i cant create a custom dimension called Service or Budget which is what i would have thought id need to do… Help :slight_smile:

Hi @oldmancook

Thanks for posting your question and thanks for the comprehensive overview. You’ve identified the core problem - how to import data and map it against something that does not exist in your Jira issues cube.

The best approach for your use case is to import this data into a separate cube specifically for your Service related time entries, rather than trying to import this data into your existing Jira Issues cube.
The reason I am suggesting a separate cube is because when creating a separate cube, you will be able to import your Service column (and other columns if needed) as a dimension and then build your report in this Custom/new Cube. Learn about the mapping rules here - Data mapping
The only restirction is that you cannot name your dimensions the same as they exist in your Jira Cube. For example, Issues Dimension should be named “Issues Custom” or similar.

If it is crucial for you to import this data into your existing Jira issues cube, then a different workaround would need to be implemented. Is the Service field contains a fixed amount of ids/members (for example you have 20 Service members that you always report on), or is this field dynamic and new Service id’s can be created regularly?

Best wishes,

Elita from support@eazybi.com