Page Comparison

Often, during the development of an integration or a special customization, people get stuck because of the lack of context. Questions appear: which user pressed on clicked the button for the next status button? Did the manager approve this item? What was the result of the calculation in the previous step? The traditional way of dealing with such questions was to create additional custom fields to keep that data, usually hidden from users (so excluded from the screens schemes), effectively adding bloat to Jira and ultimately worsening indexing - and general - performance. To help you answer these kinds of questions, SIL Simple Issue Language™ (or SIL™) acquired, starting with version 4.1.7 of the SIL EngineEngine™, a new feature, called persistent variables.

So, what's a persistent variable? In short, in an issue context, a persistent variable is a value inherently linked to the issue. Think of it as an extension of the issue fields, or - making a rather bad another analogy - an additional custom field, but internal to SILSIL™. Outside the issue context, the persistent variable becomes a global variable, accessible from all scripts. It is better to see some usage, so you will figure out can get a better grasp on what it means and how it can simplify your SIL SIL™ usage throughout your Jira integration.

Usage in an

...

issue context

Persistent variables are introduced via the persistent keyword. In order to save space, we do not allow persistent and constant modifiers to be used on the same variable, so you can't have both. A persistent variable is always modifiable.

Let's install the following post function on an easy executable action (like "Start Progress" on the default simplified workflow of Jira), and execute the transition a number of times (a normal Start-Stop progress cycle, in this example, on the same issue).

persistent number counter = 1; 
persistent boolean flag = false; 
 
description += "\n" + counter + "(" + flag + ")"; 
 
flag = !flag; 
 
counter ++;

...

So what's happening here? The truth is that the initialization of the variable happens only once. Subsequent executions will find the persistent variable initialized, and will load that particular value, and start from there. The flag will be flipped, and the counter will be incremented with each executed transition on that issue.

If you move to another issue and execute the same post function multiple timetimes, you will get a similar output. The first line of the output will still be 1(false) followed by 2(true) and so on ... which , which means that the persistent variable is linked to that issue.

Let's suppose now that we have a SIL SIL™ listener and we'll d like to use that counter variable. You can simply access it in your listener like thisin the following example:

persistent number counter;
persistent boolean flag = true; //initialization is ignored if the previous script was already executed!
//.............
/// use it in the listener like a normal variable:
counter--;

You should note Note that we didn't put any initializer; if . If the variable is already initialized, the initializer is simply not executed at all, no matter the construct. While such behavior belongs to the logic of the persistent variable, you may might find this rather strange and sometimes prone to errors. We recommend that you to use the same initializer everytime every time (maybe a constant?) so that you won't start with different values.

In conclusion, the persistent variable:

1. Persistent variable is linked to the current issue from the context,.
2. its Its initializer is executed just executed the first time (no matter the right expression, the right expression is totally utterly ignored).
3. a A persistent variable is a variable whose value survives the script, making it available in some many other scripts under the same name.

Usage

...

outside the

...

issue context

The usage outside the issue context is the samevery similar. However, due to the nature of the persistent keyword, the variable in this case becomes a global variable. Take for instance the following script, run from the SIL SIL™ Runner gadget:

persistent number counter = 1; 
persistent boolean flag = false; 
 
TEST-1.description += "\n" + counter + "(" + flag + ")"; 
 
flag = !flag; 
 
counter ++;

The Counter counter variable will be incremented as before (starting from 1) and the text above will be re-appended to the issue 'TEST-1'. However, if we change just the issue, say to 'TEST-2', the counter will maintain it's retain its previous value, incrementing from the value it stopped when you run the above for the TEST-1 issue. Just try it!

Helper

...

routines

Two We made two helper routines are available to deal ease your work with persistent varsvariables:

...

string globalCounterVar = getPersistentVar("counter");
number test_one_counter = getPersistentVar("TEST-1", "counter"); //notice the implicit cast! values are treated like strings, though!

Notes

• Although useful, persistent variables come with a small performance penalty. Don't overuse them!
• There's no way to delete a persistent var (other than direct SQL) at the moment. Think hard if you really need them.

...