I want to set so that developers cannot set zero when entering the time for the first time

[Peter Baran]

Hello, we run some trouble in our company and develoeprs are lazy to track time they had spent on tasks :) so i set up mandatory time tracking - i also attached screens how i did it. However, there is a little problem. If they simply put 0 value, they can continue, as they put real value. How to did it that for the first time they should put something bigger than 0? I only want them to do it for first time because after first solution, theere is maybe clarification and it takes zero minutes sometimes :) 

[Valeriia_Havrylenko_SaaSJet]

Hello @Peter Baran 
Welcome to the community!

If you're ok with using third-party add-ons, you can try Time in Status for Jira Cloud  developed by my SaaSJet team.

Our add-on tracks how long an issue remains in each Status, giving you a comprehensive overview of the time spent in each project stage. With this information, managers can generate detailed reports on the assignee's time to analyze the productivity of individual employees or entire teams.



This add-on  has a 30-day free trial version.
Please, let me know if you have any questions

Hope it helps,
Valeriia

[Bloompeak Support]

Hi @Peter Baran

Welcome to Atlassian Community!

You can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app.

• This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

• You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
• Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
• You can set different duration formats.
• You can export reports in CSV file format and open them in MS Excel.
• You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
• You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a free solution, you can try the limited version Status Time Free.

Hope it helps.

[Gracjan Wesołowski _HeroCoders_]

Hi @Peter Baran 

Welcome to the community!

you might consider using time-tracking apps that might have the functionality that you are looking for.

I can recommend our Clockwork Automated Time Tracking & Timesheets Free app, which offers a validator that you can use, which prevents users to transition issues if there is no time logged. 

The configuration is very simple. For details, you can refer to the documentation I've linked above. Clockwork also by default when logging time doesn't allow users to put 0 as a value.

In case you would like to keep using native Jira time tracking, you might also use a workflow condition that works with the time spent field.

To do that edit your workflow, choose the transition, click on Conditions, and Add condition button. Select the Value field and click Add. A new page will open. Select Time Spent as the Field, > as the condition, 0 as the value, and Number as the comparison type. Click Add.

Note that this condition only checks that some time was spent on the issue. It does not check when the time was logged, who logged the time, or what status the issue was in when the time was logged.

I hope that helps :)

Cheers!

Gracjan