Skip to end of metadata
Go to start of metadata

The following changes and improvements applied to all our apps are available free of charge to users who leverage the benefits of the cPrime app suite.

 Contents

Persistent Variables

Often, during the development of an integration or a special customization, people get stuck because of the lack of context. Questions appear: which user clicked the button for the next status? 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, Simple Issue Language™ (or SIL™) acquired, starting with version 4.5.0 of the SIL Engine™, 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 another analogy - an additional custom field, but internal to SIL™. Outside the issue context, the persistent variable becomes a global variable, accessible from all scripts. It is better to see some usage, so you can get a better grasp on what it means and how it can simplify your SIL™ usage throughout your Jira integration.

Other Changes

  •  We have made the version numbers for all of the Power add-ons consistent. In order to ensure binary compatibility between the SIL Engine and other Power add-ons, both should be upgraded to the same version.
  • Verified compatibility with Jira 7.12.3
  • Other minor bug fixes

Also See

  • No labels