Hi @Jack Hunter _HeroCoders_, thanks for your answer.
We're having too many worklogs with 5 or 10 minutes and it does not worth spend time workloging such little time (this means you spend same time setting the worklog than doing the task).
I don't know if other people have the same need.
OK, so we have one possible way of implementing your requirement, i.e. "blocking log works shorter than 30m".
I wonder if another solution could work too.
You mentioned that the problem is mostly with people spending time on logging the work. What if the time was logged automatically?
We have an app Clockwork Automated Timesheet (it is for Cloud but we are considering a server version) that helps to automate time tracking and therefore improve the precision of logged work.
Basically, it allows to work time in two additional ways:
It requires all the work to be done around Jira issues so there still might be a problem with splitting the work into too granular/small issues.
Let me know if automated time tracking could work in your case or if you prefer the "blocking log works shorter than 30m" solution.
We're already using a solution to automate time tracking but people doesn't feel comfortable with it (Tempo planner has a time tracker).
Also, we don't want to split the work into small issues. Many tasks are long-term tasks that are always in the same status (which means manual timer button as we have now).
I think right now, the best solution is to raise awareness about how to log hours.
Hi @jesusem ,
I am not sure if this could be done by the plugin itself. As i know there is no configuration like this.
Is it even make sense to be a default value than the null ?? Thats the point of logging your work, I mean to be exact in what you are doing !!
Hi @Christos Moysiadis, Thanks for your answer.
I couldn't find a configuration to do this so I assumed it does not exist.
We're not looking for a default value, we just need a minimum value people can log. We're having too many worklogs with 5 or 10 minutes and it does not worth spend time workloging such little time (this means you spend same time setting the worklog than doing the task).
This feature would force people and managers to group tasks and have less worklogs per day.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events