I have an assets custom field which includes two objects: “services” and “components”. (This is not the in-built Jira component but our own assets object)
Components are child objects of services. They include all the attributes of the service and one additional attribute ‘parent service’
When users raise bug tickets, they select the service/component via the custom field. Usually they will select the component. Sometimes, though, the component is not known and so the bug is raised at the service level.
So it might look something like this:
Alerts service - 2 bugs
Alert component A - 3 bugs
Alert component B - 4 bugs
My problem is how to report the sum of bug tickets at the service level - aggregating ‘component’ bugs AND adding any parent ‘service’ level bugs. (A custom hierarchy on parent service would be fine if all bugs were posted at the component level but they are not and therefore I’d like to find another way to show this data).
Are you importing additional Assets data in your Jira Issues cube or is this an Assets source with “Import object connected Jira issues” selected? In Issues cube, unfortunately I don’t see a way to connect the Service and Components objects, however, there is a possibility to build something in the Assets cube.
In Assets, what is the direction of the reference between Service and Component objects? Is Component showing up as an inbound reference or is it an outbound one? (you can check the direction of the arrow in the graph).
Thanks Nauris,
My preference is to work on the issues cube with additional assets data. In hindsight, I think it was a bad design decision by me to add the two objects in a single field. I should have kept the objects separate.
I have also created Assets cube and in that cube components have an outbound reference to services (and so services have an inbound reference from components).