The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

What will happen if Time Tracking field set as required

Qais Sami
August 14, 2018

Hi guys,

we have already an existing project with many issues distributed through all columns but the Time Tracking field was set as an optional since project creation. My question what would be the consequence if I make the Time Tracking as a required field? will it affect the issues in "In Progress" and "Testing" and other columns?

thank you

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 15, 2018

it will only affect new issues but the precise answer depends on how you make it required and you should think about that a bit. IMO it is generally not a good idea to make that field required at the Create transition. More appropriately IMO is to make it required when the issue has been 'approved' to proceed. For example, lets say you have a workflow that looks like this: To Do --> Selected for Dev --> In Progress --> Testing --> Done

I would suggest either on the transition to Selected for Dev or maybe even In Progress. For sure if you us Scrum then you want the estimate in place before starting the sprint which is built in such that you are warned if any issues in the sprint do not have an original estimate.

Qais Sami
August 15, 2018

thanks alot Jack, it's clear now.