nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Clockwork - Timesheet - Breakdown by "Status"?

Miroslav Stopka

Hi,

Im trying to create Clockwork Timesheet. I am able to filter data by Users or Projects, I am able to breakdown results by Projects or Issues. Thats perfect. But I need to breakdown the result by "Status" of filtered ISSUES. Breakdown by Custom Fields does not contain this option. How can I manage this action? Am I able to add new custom Field? How? Where?

Thank you

Accepted answers

All comments

Piotr Stefaniak [HeroCoders]

Hello Miroslav,

Thanks for using our addon. Currently Clockwork is not capable of breaking down by "Status" field. I think the best workaround would be to create a custom field (of type simple text) and use some automation/bulk edit to populate that custom field with the "stringified" name of status. That way you could use Timesheet and breakdown the results by "my mirror status custom field".

Care to describe what are you trying to achieve? Maybe there is another way...

Cheers,
Piotr Stefaniak
HeroCoders developer

Miroslav Stopka

I have to consider the solution with new custom simple text field - but I dont want to create new field just for Clockwork purposes.

Basically, we have status "READY TO CLOSE" and many more. And Im trying to create timesheets with breakdown - time on issues with READY TO CLOSE status and time on others issues.

Piotr Stefaniak [HeroCoders]

Just to doublecheck I fully understand you:

* you want to see how much time was reported on issues **when** they were in the "READY TO CLOSE" status (so: exclude time reported when issue was in i.e. "IN PROGRESS" status)

* you want to see how much time (i.e. by average) issues were staying in "READY TO CLOSE" status before someone transited them (logging work has nothing to do with that)

* you want to see how much time was reported in total for the issues that **currently** are in the "READY TO CLOSE" status

Which assumption is the correct one?

Miroslav Stopka

* you want to see how much time was reported in total (for specified time range of course) for the issues that **currently** are in the "READY TO CLOSE" status

This is the correct one

Guillermo Ermel

So "Current status" actually means the time it WAS in that status?

Guillermo Ermel

Unluckily, I found that the answer is that the breakdown is actually by CURRENT status. While some people may find this useful, I our case it means we have to resort to other tools.

Clockwork DOES have the status and time spent in each status, which is an absolute essential to understand at what point in a process we need to create improvements, but then there's no report that includes such information. It seems a breakdown by status would be an useful addition for this, but now by CURRENT status, but by the status in which the time was logged for.

This corresponds to first option in the Feb 24, 2022 response by the Hero Coder :-)

Screen Shot 2023-04-26 at 18.44.50.png

Guillermo Ermel

Hey! @Piotr Stefaniak [HeroCoders] please take a look here

Piotr Stefaniak [HeroCoders]

Hello @Guillermo Ermel,

I confirm what you're writing here. **Currently** Clockwork app does provide Timesheet breakdown (report?) by **current** status only. As per other thread in the post here: it was magnitude easier to add it into product compared to the...

> you want to see how much time was reported on issues **when** they were in the "READY TO CLOSE" status (so: exclude time reported when issue was in i.e. "IN PROGRESS" status)

...case. However, providing ability in Clockwork reports to breakdown by the "was-in-status" would be an useful addition and is something we still have on our radar. Just not the top priority.

If you want to talk this over I can bring this to attention of our Product Manager - I'm not sure if you're our customer or you're just randomly searching for specific solutions in Atlassian community, but I guess both parties might benefit from having such conversation.

Cheers,
Piotr

P.S.
Nice 🦄 purple unicorn in your Linkedin profile. I'm considering stealing the idea.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

clockwork