While using in post functions this routine will work in SIL post functions that run before the routines that save the issue in the database. The latter are default Jira post functions that can be easily recognized by their name, for instance "Update change history for an issue and store the issue in the database ", for a regular transition "Creates the issue originally ", for the "Create Issue " transition, and so on.
Description
Verifies if a field had input in the transition screen. Should only be used in transitions that require a screen.
Parameters
Return Type
Boolean
A "true" return value means that the specified field had input in the transition screen.
Examples
Example 1 - checking whether a certain custom field has any value
hasInput("customfield_12003");
Returns "true" if the customfield_12003 contains a value and "false" if the customfield_12003 is empty.
Example 2 - checking whether a ticket has comments
hasInput("comment");
Returns "true" if the Comment field contains a value and "false" if the Comment field is empty.
Example 3 - checking whether time was logged against a ticket
The following line will check whether a Time Spent field was filled out for a ticket during the transition (on the transition screen). This is useful for cases when you want to make sure that users log time when they resolve tickets.
hasInput("worklog");
If you want to show a warning under the Time Spent field for cases when the worklog wasn't entered for a ticket, consider using the following lines in the Customizing workflows.
In addition you can use the isNull routine to check whether the time was logged against the ticket before the transition.
return false, "worklog_timeLogged", "<error message>";
Custom fields must be referenced by id (customfield_id), while standard fields can be specified by one of the following keywords: summary, timetracking, security, attachment, reporter, environment, description, duedate. You can also check the Comment field, using the keyword comment.
The timetracking fields have different internal naming in this case, so you'll have to use the next mapping:
| Field | Key |
|---|---|
| estimate | timetracking_originalestimate |
| originalEstimate | timetracking_remainingestimate |
| worklog start date | worklog_startDate |
| worklog time logged | worklog_timeLogged |
See also