This routine has a very limited working scope. Since it handles transient values, it will work correct only if an interval is called starting from the moment the user clicks the Submit button on the transition screen up to the point when the issue is saved in the database. Therefore we can define the valid scope for the routine to be validators and certain post functions. It means that you will not be able to use it in conditions, SIL services, SIL listeners nor from the SIL Gadget.
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.


Verifies if a field had input in the transition screen. Should only be used in transitions that require a screen.


Return Type


A "true" return value means that the specified field had input in the transition screen.


Example 1 - checking whether a certain custom field has any value


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


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.


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.


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:









worklog start date


worklog time logged


See also