Clockify Report Parity

[KiljanK]

Since Clockify recently changed their pricing model and removed free features, many people might be looking to jump ship and become users / customers of Solidtime.

The platform already supports most of the basic features, but the "Reporting" section is a little behind. This might be especially relevant since that's also the place that lost some of its most vital features due to the pricing change.

I think it would be useful to strive for parity in that section, but i don't know how viable it is to prioritize that. Either way, i wanted to list the things that immediately stood out to me, in case this is useful for the devs:

• In Clockify Reports, the bar charts are subdivided into colored sections that match the projects' colors
  • This is especially useful when gauging efforts across projects.
• In Clockify Reports, it is possible to filter by task description text
  • This can be practical for more granular insights, since descriptions usually say a lot more than project / task information
• In Clockify Reports, it is also possible to group by more than two properties.
  • Granted, they give you access to three fields, but it's still more than Solidtime
  • It would be a really good selling point to allow for adding any number of grouping properties dynamically

[TheSpyder]

Group by date is what I miss about reports
#370

[KiljanK]

@Onatcer Thanks for the reply. I am happy to see that you'll consider merging the existing reports code that is waiting for approval.

I understand that you prioritize based on urgency, and i'm sure your the order in which you lay out the feature-implementation makes sense to you as a team member. But as an outsider, the priorization feels quite random and hard to follow.

Is there any way to gain insight into the actual priorities of the team? It's kind of hard to evaluate the usefulness of software for your team if you can never be sure if its developers intend on covering your use case in the (near) future. I have looked for a roadmap but found nothing so far.

The roadmap would also be tremendously helpful for opening up Pull Requests / Merge Requests, since it would feel extremely bad to invest time and effort into contributing, only to find out that the feature you're building won't ever get merged because it doesn't align with the platform's goals, or because the team is already working on the same feature and your code conflicts with their version.

Additionally, i was wondering if it was possible to gain influence over which features get developed in general (or their priority). I remember releases of this repo that mentioned features being "sponsored", but i have not found any info on how to do so or what budget size we would be talking about here.

Anyways, thanks for the great work and for taking the time to engage with these discussions.

Edit: hope this doesn't come off as passive aggressive

[TheSpyder]

@Onatcer the hard part has been maintaining the organisation date format in exported reports; existing reports only need it in the header not the timesheet entries. Claude took some convincing to not just make them ISO 🤣

I think the code is mostly done but I haven’t reviewed it fully (I’m going to clean up any slop before I submit it).

I’m taking a quick look at whether week grouping makes sense as well. I suspect not, because as you mentioned saved reports make that tricky. The start of the week currently depends on the logged-in user profile so public shared reports will fall back to weeks starting on Monday unless I make more changes than you’d be comfortable with.

[Onatcer]

@TheSpyder week start is already in the report dto so that should be fine, it is passed here

solidtime/app/Http/Controllers/Api/V1/Public/ReportController.php

Line 73 in 8f6d584

$report->properties->weekStart,

it currently defaults to the week_start of the user who creates it. i think adding week and month should pretty much just work in the backend, but the frontend might need some more changes. feel free to add.

[TheSpyder]

@Onatcer good to know! I'll see what I can do. Week and month did both come up as supported, but I was concerned that adding all three date/week/month might make the 'group by' menu a bit long 🤔

[TheSpyder]

That worked well, thank you for the tip 👍

I need to make time for some manual verification (there's plenty of automated tests) and then I'll open the PR.