Require time logged before closing an issue if time has not already been logged

[Lance Waldrop]

We want to require time logging before closing an issue in Jira but only if time hasn't been logged already. Is there a way to do this on the closing transition screen?

Right now we use the Time tracking field under the details pane which gives me the options of 'Time spent', 'Time remaining', and 'Date started'. We currently require 'Σ Time Spent' to be populated before closing an issue (corresponds with 'Time spent' mentioned earlier).

I would like to add the time logging details to a transition screen instead. 

The Log Work field appears closest to what I want however it doesn't take into account if time has already been logged.

I've looked at requiring 'Σ Time Spent', 'Time Spent', 'Log Work', and 'Time tracking', however I'm still required to populate the Log Work field to close an issue.

Work items can sometimes be closed within a day, sometimes there are several days of logged hours which is why I don't want require it again on close. If this is not possible I'd like to understand why so I can explain it when asked.

[Maciej Dudziak _Forgappify_]

Hi @Lance Waldrop

It is possible with Jira expression-based validator to check whether time is logged before or during the transition, but that requires 3rd party app. Sorry for the link, but I am on a train, I have answered similar question here: https://community.atlassian.com/forums/Jira-questions/Re-Re-Ensure-Time-has-been-logged-on-Transition-to-Closed/qaq-p/2838878/comment-id/1059180#M1059180

Cheers

[Tomislav Tobijas]

Hi @Lance Waldrop ,

I managed to get this to 'partially' work with Validate a field validator and by using "Match regular expression" option. I'm looking at the "Time Spent" field and by using the following expression 

^(?!0$)\d+$

Now, I say partial as this will not work if you try to log time during the transition itself > meaning, all users would need to log time before making a transition.

I'm not sure if that's a viable option or not for you but I hope it helps.
Not sure if you'll be able to get 'both' by using native functionalities.

I'm keen to see if anyone has found a different workaround for it.

Cheers,
Tobi

[Lance Waldrop]

Thanks @Tomislav Tobijas for responding. I gave that a shot and it didn't work like I was hoping.

I'm still interested in anyone suggestions but at the moment I'm leaning toward dropping 'Σ Time Spent' and just requiring 'Time Spent' on close and if they have to log hours a one additional time then so be it. Here are some screenshots from our sandbox with what's currently required and how it looks and highlighting the option I'm leaning toward using. Maybe it'll help brainstorm another suggestion:

[Tomislav Tobijas]

@Lance Waldrop if you ask me, I would maybe remove ∑ Time Spent field from the validation and leave just Time Spent together with that field being on the transition screen (if that's what is acceptable to you).

Again, maybe someone else comes with additional ideas on how this could be resolved.