How to get the field value from a specified transition screen?

[Apple]

Hi Jira experts,

I'm configuring the workflow to improve team efficiency. Do you know how to get the value from a specified transition screen? I want to popup error/warning message when team member is trying to set an unreansonable value.

Thanks.

[Jack Brickey]

How do you define an unreasonable value? I wonder if the right approach is to construct the field to reasonable values. You can have a transition screen that pops up at the moment of transition that requires certain input. And you could have a validator on that transition that will require input.

[Apple]

As I understand, "requires certain input" means you must set several specified fields in the screen, right? But how about the filled values? For example, it's unreasonable for one task end at 2000/01/01 as we are in 2021 now.

[Daniel Ebers]

Hi @Apple

if the requirement is specifically for dates you can work with a "validator" in a workflow, there especially a"Date Compare Validator"

This kind of validator is included in Jira Cloud Free plan - for more complex validators you will be needing an App which is available from Marketplace.

Example: The above shown validator definition makes sure the due date is greater than the current date/time.

You can learn more about Validators here - please note they only apply to company-managed projects:

• Use workflow validators for company-managed projects
  https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-validators-for-company-managed-projects/

Regards,
Daniel

[Apple]

Thanks @Daniel Ebers 

I have tried Validator before and it's helpful to resolve some issues. But I still have no idea about below scenario, as you see, it's a workflow screen for Done transition, Time Spent 1000w is obvious unreasonable. 

I tried Validator also but failed to get the filled value 1000w. Do you have any idea? I want to trigger error message when user click on the button Done.

Thanks again.

[Daniel Ebers]

Finally it will boil down to the approach I showed earlier - if this does not work a separate App might be the way to go.

There will be also a distinction between wrong value (for example) in comparison to a likely too great value. Am I right you consider 1000w as a to great value (because technically/basically) this is fine.
If so, you probably would need to specify more complex rules on which amounts of time are allowed and not (seemingly 1000w are are to great range).