How do I compute the time that went into a customer relationship in a month?
Asked by Bj?rn Goerke:

- in the field time spent we report the time that went into a ticket

- in the field organization we note the client we worked for

now I would like to find out how much time was invested in each organization through working on the respective tickets. The time spent in a given month would be the ideal figure. But I could also live with a number for the amount of time that was invested in the tickets that were created in a given month - which can differ as the tickets sometimes get opened in one month and then get close the month later.


Answers:
author: Marc - Devoteam
body: Hi [@Bj?rn Goerke](/t5/user/viewprofilepage/user-id/5443454)

You could look at an automation and do a lookup on each customer, but this is automation limit heavy and the lookup function can only handle a max of a 100 issues.

And count all the worklogs in the found issues via advanced formatting in each automation.

The suggestion of [@Dwight Holman](/t5/user/viewprofilepage/user-id/655415) is also valid if you have Tempo, or you could look add other marketplace apps for reporting or to able to export data to a BI tool if you have one, but all at a cost.

comments: author: Bj?rn Goerke
body: thank you, Marc! I will look into the automation functions.


author: Dwight Holman
body: We have done this using the Tempo Timesheet app:

[How to connect Worklogs to a Tempo Customer Account](https://tempo-io.atlassian.net/wiki/spaces/KB/pages/1085046794/Tempo+Accounts+-+how+to+connect+worklogs+to+an+Account?src=search)

But I'm not sure if it fully integrates with JSM Organizations - so you might need to manually set the Tempo Account field (or setup automation to do that).

I believe other apps are available that do this. Or you could check out other community discussion about this:

[Work log extraction by month](https://community.atlassian.com/t5/Jira-Software-questions/Work-log-extraction-by-month/qaq-p/2162946)

comments: author: Bj?rn Goerke
body: thank you, Dwight! Sounds very good. I will look into this.


author: Hannes Obweger - JXL for Jira
body: Hi [@Bj?rn Goerke](/t5/user/viewprofilepage/user-id/5443454)

if you're open to solutions from the Atlassian Marketplace, you may want to have a look at the app that my team and I are working on, [JXL for Jira](https://marketplace.atlassian.com/apps/1224710?hosting=cloud&tab=overview&utm_source=atlassian-community&utm_medium=referral&utm_content=2627681).

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields - including all JSM fields - much like you'd do in e.g. Excel or Google Sheets. It also comes with a number of advanced features, including support for (configurable) *issue hierarchies* , *issue grouping* by any issue field(s), *sum-ups* , or *conditional formatting*.

With these, you can build a report like e.g. this in just a couple of clicks:

![time-spent-per-organisation.gif](https://community.atlassian.com/t5/image/serverpage/image-id/311070i9EBC56E8747D7A04/image-size/large?v=v2&px=999 "time-spent-per-organisation.gif")

This is just one of a virtually endless number of possible reports; you can also group by any other field, configure different sum-up styles, etc. etc. As every JXL sheet is powered by either a saved filter or a JQL statement, you can also easily create cross-project views.

Any questions just let me know,

Best,

Hannes


Tags: cloud

jira-service-management

jira-service-management-cloud