| Info | ||
|---|---|---|
| ||
This routine is available since
|
Syntax
lfWatch(field, relatedFields, scriptPath[,javaScriptEvents]);
Description
| Excerpt |
|---|
| Attach listeners for the events that you give as parameters in the function. |
If you don’t give any event, it attaches listeners to “change” event (triggered when the issue is updated).
...
This SIL script receives the values for the relatedFields and you can use them as: argv[field].
Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
| field | String | Yes | The field to listen. |
| relatedFields | Array String | Yes | The dependent fields required for the given field. |
| scriptPath | String | Yes | The script source to run when the event is triggered. |
| javaScriptEvents | Array | No | The events to listen to. It's any JavaScript event (check this list for references) |
| Warning | ||
|---|---|---|
| ||
When using the "change" event on a "labels type" field (Fix Versions, Affected Versions, Labels, Components, etc.), the event will never trigger when a label is deleted, but only when labels are added. We have noticed that for these fields the "focusin" event closely matches the behavior expected for the "change" event. |
...
As we said before, the values from the relatedFields are accessed as argv[field]. For multiple values fields like components or affectedVersions the value returned is in the following format: val1|val2|val3.
| Info | ||
|---|---|---|
| ||
For more information, see How 'Live Fields' work. |
See Also:
| Filter by label (Content by label) | ||||
|---|---|---|---|---|
|