nützliche links
Search the documentation
There is no content with the specified labels
Compatibility
- Added support for Jira 8.12
Improvements
- Access the internal ID of your Jira projects by using projectIDFromKey() either as a field code or parser function
- Access the sprint completion date through a brand new field code
- The function usersWithEmail() now ignores the case which makes it easier to find the users you are looking for
- Smart improvements in terms of logging and security
Bug fixes
- The function timeInStatus() returned wrong results in case an issue was never transitioned
- The functions fieldHistory() and previousValue() returned unexpected results for user picker fields
- Improvements to the Automation Rules configuration
Find more release notes in our Version History section.
Bug fixes
- Expression parser fields were broken in 2.9.1 when editing some workflow functions
Find more release notes in our Version History section.
Improvements
- Extended support for Botron's Configuration Manager, now including versions, components and custom field options
- The child level of cascading selects fields is now validated as required only when there are child options available
- Added warning in case of configuring self-referencing expressions in calculated custom fields
- Minor UI updates
Bug fixes
- The selected transition could be cleared unintentionally when editing a Transition issues post function
- Parent fields were not avaible in the Field Changed Event trigger
Find more release notes in our Version History section.
Direct download from Marketplace
"Building the best processes to support your teams."
- Automation rules are now available within Jira Workflow Toolbox -
A year ago we released our app Automation Toolbox to not only enable you to automate your daily work in Jira workflows but also match your business processes with automation rules listening to Jira's various events like field, issue, project, and system events.
With the release of Jira Workflow Toolbox 2.9.0, Automation Toolbox will become an integral part of Jira Workflow Toolbox because we decided you should not need two apps for one common goal: Building the best processes to support your teams.
But it is not just a merge... it's a match!
With the merge of the two products, Jira Workflow Toolbox has become the complete automation solution for your Jira on Server and Data Center platforms. The name remains the same, but now you can go way beyond your Jira workflows.
New features
- Automation rules are now available within JWT in order to perform Actions based on Triggers
Improvements
- A Get started page was added to serve as a central hub for accessing all JWT-related functions
- An option to suppress the default Jira email subject prefix was added to the Send an email post function
Bug fixes
- Setting components did not work properly when using special characters within component names
- Cascading select list field names were not resolved correctly within our view screens
- Post functions using the Target issue parameter could result in corrupt snapshots for Botron's Configuration Manager for Jira
- The Field required or changed validator did not show the red asterisk for certain field types
- The Transition issues post function lost certain parameters when it was being edited
Find more release notes in our Version History section.
New features
- Added RUN_AS_LANG as a new language parameter to the expression parser
- Added RUN_AS_LOCAL as a new time zone parameter to the expression parser
Bug fixes
- The Send an email post function did not include zip files attached during the transition
- The Assign to Project Role post function was always executed by the current user
- The Assign to Project Role post function didn't work properly when selecting Last user or Previous user in project role
- The timeInStatus function returned negative values if the initial status was changed in the workflow
- The Epic Link field could not be edited inline within the 3rd party app Structure by ALM Works
- Adding a Transition issue post function caused problems in case the status or transition selection was not changed
Find more release notes in our Version History section.
New features
- Added support for Botron's Configuration Manager for Jira (see our documentation)
- Added support for Jira 8.6.x
Bug fixes
- The Fields required or changed validator did not work properly when using version fields after upgrading to JWT version 2.7.1
- Jira Service Desk approval emails did not work properly when using JWT-related post functions on the transition to the approval step
Find more release notes in our Version History section.
Direct download from Marketplace
Bug fixes
- The function dateTimeToString() generated an error
- All functions returning users now exclude inactive users
- Conditions based on JQL expressions did not work properly when a query included an ORDER BY clause
- Multi-level cascading select fields from Sourcesense (3rd party app) could not be set
- The red asterisk in the Fields required or changed validator was not shown for some fields
- Fields required or change validator did not work properly for fields including a comma in their names
- Message to show at failed validation in validators was not shown next to the specified field in the create transition
- Performance improvements for the timeInStatus() function
- Conditions Only users in a field/Except users in field evaluated against the changed issue instead of the original issue
Find more release notes in our Version History section.
Direct download from Marketplace
"Small step for a validator, giant leap for Jira users"
- Show a red asterisk * and a custom error message next to fields that are only required in a specific transition -
New features
- The Field is/isn't initialized validator was renamed to Fields required or changed
- The Field is/isn't initialized condition was renamed to Fields required
- The Fields required or changed validator and the Fields required condition can now validate multiple fields
- The field/s configured as required in the Fields required or changed validator is/are marked with an asterisk (*) in the transition screen
Improvements
- An optional delayed execution was added to the Move issues post function
- In the Send mail post function all the inactive users and email addresses with an incorrect format are filtered out
Bug fixes
- A Null-Pointer Exception was thrown in the Create issues post function while copying options from deleted custom fields
- The addDaysSkippingWeekends function ran into a timeout for large numbers
- The selected issue type was not set in the corresponding select element while editing a Move issues post function
- The Move issues post function produced corrupt issues when the status was changed without changing the workflow
- The Field is/isn't initialized or has/hasn't been modified validator did not work properly for text fields with multiple lines in Chrome browser
- The Move issues post function used to move an issue to a selected project with a retained issue type even though that issue type was not available in the target project
Find more release notes in our Version History section.
Direct download from Marketplace
Bug fixes
- Last comment's visibility restrictions did not return the Service Desk visibility of a transition comment
- Value type Standard did not work properly when setting fields in the Create issues post function
- Disabling and enabling the app could produce a "Service proxy has been destroyed" error
Find more release notes in our Version History section.
Bug fixes
- Setting Clear field value as value type in distinct post functions did not work properly for version and component fields
- Post functions stopped executing when trying to access a non-existent (e.g. deleted) custom field
- Executing Jira Workflow Toolbox post functions via the Workflow Enhancer for Jira app did not work properly
Find more release notes in our Version History section .
Improvements
- The Move issues post function now supports parsed text to be used to determine target project, issue type and status selection
- The Move issues post function now shows custom error message on the screen when issues can't be moved due to incompatibility
- The expression parser and the field injector now support the Resolution Date
- The Send an Email post function now supports mixed parsing mode when using personalized mode
New expressions in the parser
Function | Returned Value |
---|---|
setBoolean(string variable_name, boolean value) : boolean | Creates a variable named variable_name for storing a boolean value, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getBoolean(string variable_name) : boolean | Returns the value stored in a boolean variable named variable_name, which was previously created using the setBoolean() function. Example: |
setNumber(string variable_name, number value) : number | Creates a variable named variable_name for storing a number, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getNumber(string variable_name) : number | Returns the value stored in a numeric variable named variable_name, which was previously created using the setNumber() function. Example: |
setString(string variable_name, string value) : string | Creates a variable named variable_name for storing a string, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getString(string variable_name) : string | Returns the value stored in string variable named variable_name, which was previously created using the setString() function. Example: |
setNumberList(string variable_name, number list value) : number list | Creates a variable named variable_name for storing a number list, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getNumberList(string variable_name) : number list | Returns the value stored in number list variable named variable_name, which was previously created using the setNumberList() function. Example: |
setStringList(string variable_name, string list value) : string list | Creates a variable named variable_name for storing a string list, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getStringList(string variable_name) : string list | Returns the value stored in string list variable named variable_name, which was previously created using the setStringList() function. Example: |
setIssueList(string variable_name, issue list value) : issue list | Creates a variable named variable_name for storing an issue list, and assigns it a value, which is also returned in order to be used within an expression. Example: |
getIssueList(string variable_name) : issue list | Returns the value stored in issue list variable named variable_name, which was previously created using setIssueList() function. Example: |
weekOfTheYear(number t, number firstDayOfTheWeek, number minimalDaysInFirstWeek, timeZone time_zone) : number | Returns the week of the year of the date-time t in a certain time_zone. The parameter firstDayOfTheWeek represents the first day of the week, e.g.: Example: Example: Example: |
dayOfTheYear(number t, timeZone time_zone) : number | Returns the day of the year of date-time t in a certain time_zone, e.g. for January 1st the value returned will be 1. Example: |
timeInValue(string field field, boolean expression predicate) : number | Returns the number of milliseconds a string field with code Example: Example: Example: |
timeInValue(number field field, boolean expression predicate) : number | Returns the number of milliseconds a number or date-time field with code Example: Example: Example: |
timeInValue(string field field, issue list issues, boolean expression predicate) : number | Returns the sum of milliseconds a string field with code Example: Example: Example: |
timeInValue(number field field, issue list issues, boolean expression predicate) : number | Returns the sum of milliseconds a number or date-time field with code {nnnnn} has had a value satisfying a boolean expression predicate in distinct issues, where the numeric value of the field with code {nnnnn} is represented by ^ .Example: Example: Example: |
timeInValue(string field field, boolean expression predicate, string schedule_name, timeZone time_zone) : number | Returns the number of milliseconds a string field with code Example: Example: Example: |
timeInValue(number field field, boolean expression predicate, string schedule_name, timeZone time_zone) : number | Returns the number of milliseconds of a number or date-time field with code Example: Example: Example: |
timeInValue(string field field, issue list issues, boolean expression predicate, string schedule_name, timeZone time_zone) : number | Returns the sum of milliseconds a string field with code Example: Example: Example: |
timeInValue(number field field, issue list issues, boolean expression predicate, string schedule_name, timeZone time_zone) : number | Returns the sum of milliseconds number or date-time field with code Example: Example: Example: |
fieldChangeTimes(string field field, boolean expression predicate) : number list | Returns the timestamps of when a string value of field with code Example: Example: Example: |
fieldChangeTimes(number field field, boolean expression predicate) : number list | Returns the timestamps of when a numeric / date-time value of field with code Example: Example: |
fieldChangeTimes(string field field, issue list issues, boolean expression predicate) : number list | Returns the timestamps of when a string value of fields with code Example: Example: f Example: |
fieldChangeTimes(number field field, issue list issues, boolean expression predicate) : number list | Returns the timestamps of when a numeric value of fields with code Example: Example: |
lastFieldChangeTime(string field field) : number | Returns the timestamp of most recent value update of a field with code %{00000}. Example: |
unreleasedVersionsBySequence() : string list | Returns a string list with the unreleased versions in the current project with the default order. Only non-archived versions are returned. The first version in the list is the lowest version in the version table. |
releasedVersionsBySequence() : string list | Returns a string list with the released versions in the current project with the default order. Only non-archived versions are returned. The first version in the list is the lowest version in the version table. |
Bug fixes
- Using the Move issues post function on individual sub-tasks (without moving the parent) resulting resulted in incompatible parent-child relationships. Moving individual sub-tasks is currently not available
- Issues were not correctly moved to newly created Epics.
- Custom fields could be set to values not available/valid in their respective field context using the Move issues post function
- Setting the "Sprint ID" to a value equal or greater than 1000 produced an error
- Incorrect error messages were logged when detecting deleted custom fields
Find more release notes in our Version History section.
Direct download from Marketplace
Bug fixes
- While performing the Move issues post function all the custom field values of the moved issue were deleted
Find more release notes in our Version History section.
Bug fixes
- Create issues and subtasks post function bug when the option inherit rest of the fields was selected
Find more release notes in our Version History section.
Find more release notes in our Version History section.
Find more Release Notes in our Version History section.
JIRA Workflow Toolbox provides a rich set of conditions, validators and post-functions for designing complex workflows on JIRA. It also supplies an easy and powerful mechanism to implement metadata in JIRA projects: Project Properties, making it possible to customize workflows behavior as a function of the value these properties in each project. It improves dramatically the flexibility and reusability of your workflows. A set of JQL functions is also available for making queries on project properties.
Amazing Things You Can Do using JIRA Workflow Toolbox
JIRA Workflow Toolbox allows to do things you wouldn't believe possible that easily before.
Project Properties
Project Properties is a simple mechanism implemented by JIRA Workflow Toolbox, to include machine readable key-value pairsinto projects description, thereby operating as an effective way for adding metadata to your JIRA projects.
Virtual Fields
JIRA Workflow Toolbox provides a set of special fields, called Virtual Fields, making accessible the most interesting properties of issues, projects and users, the same way as ordinary custom fields. Virtual fields may be read and written by all the plugin's modules the same way ordinary custom fields are.
Trying and Purchasing the Plugin
You can ask for a 1 month long trial license for the plugin at Atlassian Marketplace. Trial licenses can be renewed in case your evaluation process requires longer than trial license duration. JIRA Workflow Toolbox can be purchased at Atlassian Marketplace. Unfortunately not all countries are supported by Atlassian Marketplace. In case you are in one of the non-supported countries, you can purchase the plugin contacting directly an Atlassian Expert in your region.
Support SLA
Support to legitimate users of JIRA Workflow Toolbox will be provided in accordance with the following Service Level Agreement. Non-public questions or support requests may be made at: support@workflowarts.com. Please, don't hesitate to ask for support if you are evaluating the plugin.
I'm Fidel Castro Armario, the developer of JIRA Workflow Toolbox. Please, feel free to contact me at any time if you have any question, need support, or want to do any suggestion about the plugin. Nevertheless, I will thank you for using JIRA Workflow Toolbox Help Forum, if you feel your question and my answer may be useful to other users of the plugin.
Featured Pages
Error rendering macro 'contentbylabel'
parameters should not be empty