Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

7th November 2019

The beecom team Our Product team is happy to announce the release of JSU 2.18.0, which is now ready for download on the Marketplace.

New FeatureIssue Relation for Clear Field Value Post-Function

We also introduced the Issue Relation functionality to the Clear Field Value Post-Function, well known in other existing Post-Function e.g. Copy Value From Other Field Post-Function. For example, instead of clearing a value within the issue during the post-function, you can clear the value in all Sub-Tasks.

'Perform as user' - impersonation - in all Post-Functions

We extended the functionality 'Perform as user' to all Post-Functions. For example, you can now simply Update a Field in an other another Project where you do not have permission. Common Use-Case is a Developer & Service-Desk Project. You can update a Status Field in the Service-Desk Project when a Developer fixed an Issue. The developer does not require permission to in the Service-Desk Project instead an service-user can be usedinstead a technical user can perform the update.

'User is in Any Users' Condition

We introduced a new Condition 'User is in Any Users'. You can select which users can see and perform a Transition. This works best in combination with 'Perform as user' (impersonation). You can hide a transition from all users and only the impersonated (technical) user can use the transition.

Issue Relation for Clear Field Value Post-Function

We also introduced the Issue Relation functionality to the Clear Field Value Post-Function, well known in other existing Post-Function e.g. Copy Value From Other Field Post-Function. For example, instead of clearing a value within the issue during the post-function, you can clear the value in all Sub-Tasks.

Bugfixes

  • Fixed Position of Field required marker (red asterisk) in Tabs for Jira 8.4+.
  • Fixed duplicated change history entries if a Version Custom Field was cleared.
  • Fixed not required change history entries in relation to Date Custom Fields.