Timesheet Restriction - Custom field planned go live date should not more than 30 days

[Venkatasrinivasarao Nseit]

Dear Team,

users are logging times on issues, which issues planned go live date are passed. Kindly suggest any restriction to log time on issues planned go live date should be less than 30 days.

[Trudy Claspill]

Hello @Venkatasrinivasarao Nseit 

Welcome to the Atlassian community.

There is no native feature related to the native time tracking option that enables you to prevent time being logged on an issue based on the date in a field in the issue.

If the Go Live Date being in the past corresponds to the issue Status also being set to a particular value, then you could use Workflow Properties to prevent the logging of work while the issue is in the specified Status.

https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

A work around would be to create an Automation Rule triggered by Work Logged. In that rule you can check if the Go Live date is in the past or within the next 30 days. If the Go Live date is in the past or not within the next 30 days, the automation rule could delete the work log and send a message to the person that logged the time alerting them that logging time is not allowed for such issues.

https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/