Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,300,026
Community Members
 
Community Events
165
Community Groups

How to make time tracking mandatory

I have found some topics about this but none seem te work for me. 

I want to achieve that developers have to update their time tracking (by clicking time tracking and entering a value in the "time spent" field.)

 

In the workflow and more specific for the transitions I find the validators where I can set that the field "time spent" should be updated by the user before being able to transition the issue (eg from doing to review). 

But when I set this up it blocks the transition even when time has been logged.

It is confusing because in Jira you have a field "Time tracking" which shows the total logged time with a progress bar.

But if you want to log time you can click on this and a modal opens. This modal shows 2 fields: time spent and time remaining. 

The time spent must be entered but after entering it, it is empty again (which is normal behaviour after submitting a value). The entered time is added to the "time tracking".

So I don't think I can validate on "time spent" because it is always empty but I should validate on "time tracking has been updated" or something like that. 

How can I achieve that developers must update the worked time (work log?) before making the transition? 

2020-07-28 16_55_38-Actieve projecten - Agile Board - Jira.png

3 answers

This can be achieved when you modify time spent exactly during transition:

1. Add a screen with 'Log Work' field to the transition.

2. Look at the time spent field - it must be modified.

 

Example validator:

The transition requires the following criteria to be valid

Field Time Spent should be modified during the transition.

Error message: Time must be logged!.

Apologies Jakub - this is correct and does work

For the benefit of others as this in not the most intuitive  process, the confusion I found here is that with other fields you are able to set validators that act on the screen you are already on which trigger a small notification in the bottom right of the screen:

 

image.png

This is the approach I was trying with Time Tracking field - but this does not work - you get the warning notification as per the screenshot above but are never able to progress beyond this.

The solution Jakub put me on to is to:

  • add a totally brand new screen (via the the Settings cog (top right of screen) => Issues => Screens => Add Screen)
  • add a Log Work field to this
  • go to the workflow editor, select the transition and set the screen there to the new screen you just created

image.png

Now when you transition the ticket you will see the entirely new screen and the validator will work on this.

image.png

In the workflow I don't have the option to select a screen for a transition. I don't see the thing the red arrow above is pointing at.

 

update: never mind, you have to edit the transition first and then select a screen in the popup :-) 

Hi all,

I had the same problem as above as I could not locate the "Time Spent" field in the list of fields.

It has now come to my attention that it is not just a dropdown but a multi-select form. If you start typing, you can select your field (see screenshot).

Good luck!

Screenshot 2022-04-06 at 19.02.06.png

 

0 votes
Jack Brickey Community Leader Jul 28, 2020

What Validator are you using? Keep in mind that if you use “modified” then the user must actually change the field  during the transition. Simply having a value entered before the transition will not suffice.

Hi Jack

the goal is that because a transition implies that work has been done on an issue, the user must log his work. This troughout the workflow (todo-doing-review-test-done)

 

If I only check on value entered, and this is done from doing to review, then there is no validation that the reviewer also logs his work (because there is already a value). But the review time must be logged as well. Therefore I wanted to use the modified validator.

I want to use

Field has been modified Validator : Field value must be changed during the transition.

 

And then apply it to the correct field but I don't see a "time tracking" field. Only timespent and "sum" time spent and when I use them the transition is always blocked, even if time is logged right before the transition, so I don't know which is the name of the field I must validate.

Has this been resolved? I am running into a similar issue, not having 'Time Tracking' as the field to validate.

No, not resolved unfortunately. I don't know if it is possible.

Thanks for this thread! Actually I'm facing this problem as well. Actually its such a basic thing as such. 

 

Please help if there is a solution to this.

I'm having this exact same issue - has anybody found a resolution?

 

Thanks

Hi,

 

as Jack already wrote: "Keep in mind that if you use “modified” then the user must actually change the field during the transition. Simply having a value entered before the transition will not suffice."

 

If you modify the field during transition It becomes quite simple:

1. Add a screen with 'Log Work' field to the transition.

2. Look at the time spent field - it must be modified.

 

Example validator:

The transition requires the following criteria to be valid

Field Time Spent should be modified during the transition.

Error message: Time must be logged!.

Thanks Jakub - this post is with particular reference to the built in Time Tracking field type - it looks like you are resolving this by using a new custom field you call 'Log Work'

 

With the Time Tracking field the transition validator doesn't work either with the required or modified validators

image.png

Hi Paul, this is not a custom field.

 

This is a standard Jira field from the new issue view.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

31 views 0 2
Read article

Community Events

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

Events near you