+1Hi,
It was a major feature the possibility of crossing data from different metrics
If we select a metric of “Timesheet” module (1), when adding 2nd metric (2) we only have available metrics inside the “TimeSheet”
Example of Usecase:
The use of Custom Fields in Tickets Module, like “Company” cannot be crossed by TimeSheet by Company, making it impossible to Know Hours for Billing by Company.
+8
+1Not an issue anymore, thanks for the new updates
+8+8This is a really important limitation. As far as I’ve tested, most native analytics setups don’t support joining datasets across modules (like Tickets + Timesheets) within a single widget unless there’s a predefined relationship or shared schema.
A practical workaround is to handle this outside the system:
In some cases, even lightweight preprocessing (like cleaning, structuring, or standardizing text-based fields) makes a noticeable difference in how usable the final report becomes. I’ve personally experimented with small utilities (e.g., letras-diferente dot net) to normalize and format outputs before feeding them into reports, not a full data solution, but helpful for consistency and readability.
That said, native cross-module querying (or even a basic join capability in analytics widgets) would significantly reduce this overhead and make reporting much more powerful.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
