| Table plus | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
| Warning |
|---|
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. |
Description
| Excerpt | ||
|---|---|---|
| ||
Verifies if a field had input in the transition screen. |
Verifies if a field had input in the transition screen. Should only be used in transitions that require a screen.
...
| Table plus | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
|
Return Type
Boolean
A "true" return value means that the specified field had input in the transition screen.
...
| Code Block |
|---|
return false, "worklog_timeLogged", "<error message>"; |
| Note |
|---|
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
| Filter by label (Content by label) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|