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; } } }

Limit Timespent on Jira issue

Zaur Suleymanov_lq3sgc

Is there any way to apply Time spent limit to Jira issue? If not, is there an option to send at least notification when agreed limit is exceeded?

Accepted answers

tokcum

Dear Zaur,

I’m afraid this is not possible out of the box.

This is a link to a thread from last year with a very similar question.

https://community.atlassian.com/t5/Jira-questions/Setting-maximum-work-log-time-for-issue/qaq-p/982355

In fact I would not recommend to restrict logging work in this way because this tends to foster inappropriate behavior.

I like your second approach with getting informed about issues being overbooked. I’m not aware of how you could be notified immediately in such a case. In my environment I prepared issue filters for that and present the results on dashboards and allows users to subscribe the filter in case they like to get informed via mail instead of having to check the dashboard.

I hope this is of some help to you.

Kind regards,

Tobias

All comments

tokcum

Dear Zaur,

I’m afraid this is not possible out of the box.

This is a link to a thread from last year with a very similar question.

https://community.atlassian.com/t5/Jira-questions/Setting-maximum-work-log-time-for-issue/qaq-p/982355

In fact I would not recommend to restrict logging work in this way because this tends to foster inappropriate behavior.

I hope this is of some help to you.

Kind regards,

Tobias

Zaur Suleymanov_lq3sgc

Thank you Tobias for your advise! I will also try to figure out at least some notification with Jira Automation.

tokcum

Sure, if you have Jira Automation at hands their are a lot of opportunities. I use it to calculate ratios of booked time to original estimates. With this approach I’m able to point out the real mismatches based on thresholds, e. g. 10% might be okay, but 20% is a warning and more needs management attention.

If you are interested in this approach, I‘m happy to share it with you.

Have a nice weekend.

Zaur Suleymanov_lq3sgc

Thank you, Tobias! That's sounds interesting! Can you share how you could do that?