🚀 JWT 3.0 is out 🚀 

The app was completely overhauled, and so was the documentation: Jira Workflow Toolbox (Server/Data Center) Home

The page you are viewing is still valid for all app versions prior to 3.0.

[2015-10-07] Released Jira Workflow Toolbox 2.2

New features

  • Added new parser functions:
FUNCTION RETURNED VALUE
projectProperty(string property_name, string project_key) : string Returns a string with the value of project property with name property_name in project with key project_key. Shows an error message if project property doesn't exist.
Example: projectProperty("maxNumberOfReopenings", "CRM") returns "3", provided there is a string {maxNumberOfReopenings=3} in the description of project with key "CRM".
projectPropertyExists(string property_name) : boolean Returns true only if there is a project property with name property_name in current issue's project, i.e., if project's description contains a string like {property_name=value}.
Example: projectPropertyExists("maxNumberOfReopenings") returns true only if there is a string like {maxNumberOfReopenings=x} in the description of current issue's project.
projectPropertyExists(string property_name, string project_key) : boolean Returns true only if there is a project property with name property_name in project with key project_key.
Example: projectPropertyExists("maxNumberOfReopenings", "CRM") returns true only if there is a string like {maxNumberOfReopenings=x} in the description of project with key "CRM".

Improvements

  • Compatibility with Jira 7. The plugin now is compatible with versions of Jira from 6.2.3 to Jira 7.0.
  • Issue #175: Post-function " Add a comment" now supports Jira Service Desk comment visibility modes: internal and public.
  • Virtual fields "New comment" and "Last comment" now provides an optional parameter for setting comment visibility. To do it add ": {visibility=visibility_value}" at the end of the text written in these virtual fields. visibility_value is the name of a group, name of a project role, or values "internal" or "public" (without double quotes) for Jira Service Desk comments.
  • Virtual field "Last comment's visibility restriction" now supports Jira Service Desk (JSD) comments. Values admitted for setting JSD comments are public or jsd_public and internal or jsd_internal.
  • Support for Jira Suite Utilities's "Location Select List" custom fields.

Bug Fixes

  • Parameter "Evaluate all the setting rules" in post-function " Set a field as a function of other fields" should be enabled/disabled automatically depending on the type of target field.
  • Virtual field "Last comment's visibility restriction" wasn't working properly with some versions of Jira