How do I compute the time that went into a customer relationship in a month?

[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.

[Marc - Devoteam]

Hi @Björn Goerke 

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 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.

[Björn Goerke]

thank you, Marc! I will look into the automation functions.

[Dwight Holman]

We have done this using the Tempo Timesheet app:

How to connect Worklogs to a Tempo Customer Account

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

[Björn Goerke]

thank you, Dwight! Sounds very good. I will look into this.

[Hannes Obweger - JXL for Jira]

Hi @Björn Goerke

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.

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:

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