Skip to end of metadata
Go to start of metadata

[2016-08-23] Released Jira Workflow Toolbox 2.2.16

Improvements

  • Function hasChanged(field_code) now supports the following system fields:
    • Summary
    • Description
    • Due date
    • Priority
    • Environment
    • Fixed Versions
    • Affected Versions
    • Components
    • Labels
    • Security Level
    • Resolution
    • Reporter
    • Assignee

      Until now this function worked only with custom fields.

      Function hasChanged(field_code) is used when we set a validation that is incompatible with a condition in a same transition, typically when validating a value entered in the transition screen. When Jira evaluates the validations in a transition, it also reevaluates the conditions, and if they are not satisfied an Action X is invalid error message is shown and the transition is not executed.

      Example: Let's suppose we have a boolean condition like {00012} = null (i.e., Due date = null) in a transition, so that it's only shown when Due date is empty. This transition also has a transition screen containing field Due date, and a boolean validation {00012} != null, in order to make Due date required in the transition.
      The configuration described above will not work, since both condition and validation are mutually incompatible. We can fix it replacing the boolean condition with {00012} = null OR hasChanged(%{00012}).

      Some real examples: Issue #363 and Issue #260.

Bug Fixes

  • Issue #324 - Transition executions triggered by post-functions stop working requiring plugin reinstall
  • Issue #334 - Post-function failed to progress an issue
  • Issue #388 - Jira server might hang up when executing features based on JQL queries returning a very big number of issues
  • Send an email post-function doesn't work when using project roles for selecting To and Cc recipients
  • Minor UI problems.
  • A bug fix in the parser allows a vey compact syntax for summing numeric fields when some of them may be uninitialized. These are the 3 ways available for summing 3 numeric fields:
Expression Returned Value Notes
{10000} + {10001} + {10003} Formula for summing 3 numeric custom fields when we are certain that all 3 the fields are initialized. In case any of these fields is not initialized, an error is raised and any of the following 2 expression examples should be used. {10000}, {10001} and {10003} are three numeric custom field.
({10000} = null ? 0 : {10000}) + ({10001} = null ? 0 : {10001}) + ({10003} = null ? 0 : {10003}) Formula for summing 3 numeric custom fields when some of them may be uninitialized. When any of this fields is not initialized a zero value is assumed.

{10000}, {10001} and {10003} are three numeric custom field.
sum([{10000}, {10001}, {10003}]) A more compact syntax for summing 3 numeric custom fields when some of them may be uninitialized.
Version JWT Release Notes 2.2.16 or higher is required.
{10000}, {10001} and {10003} are three numeric custom field.