We have an unusual scenario. We recently added some custom fields to track additional details on Jira tasks. The custom fields are required. So, for any new tasks they are present. However, on older tasks that are still in progress (there are hundreds if not thousands as we have many users and projects in our Jira instance) those custom fields are not filled out. The teams are supposed to be going back and updating the older tasks with the custom fields so they can be tracked properly. This is a more difficult task than anticipated and we would like to "push" the users to get that task completed. To do so, we are considering not allowing them to enter their work log time on any task that doesn't have one of the custom fields populated. This will force them to make the update to the custom field on that task.
I know about the ways to use a property on the workflow status or transition to to not allow the worklog, but I can't find a way to restrict that worklog entry if a custom field is empty.
Any ideas? It never hurts to ask (yes, I did search here and other sites to find a similar answer).
Thanks in advance.
For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...
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