Jira Data Center 6.3 - 7.2.15
Turn ideas into workflows: great set of conditions, validators, post functions & custom fields. Create, transition & update issues
Turn ideas into workflows: great set of conditions, validators, post functions & custom fields. Create, transition & update issues
Conditions & Validators
Post Functions: Create, Transition & Update Issues
3 Custom Field types: numeric, text & date/time
Insert dependencies on linked issues, subtasks and JQL queries, evaluate complex time, math formulas, and regular expressions, check roles agains user, multi-user and group fields, and much more with JWT.
Create issues on transition. Copy, set or update field values in current or related issues. Do more with issue links, project/user properties and send email. No need for groovy scripting.
Display any calculated value depending on other fields in current or linked issues, sub-tasks, epics, stories & JQL selected issues. Create highly configurable currency, duration and text read-only fields
Conditions & Validators
Post Functions: Create, Transition & Update Issues
3 Custom Field types: numeric, text & date/time
Insert dependencies on linked issues, subtasks and JQL queries, evaluate complex time, math formulas, and regular expressions, check roles agains user, multi-user and group fields, and much more with JWT.
Create issues on transition. Copy, set or update field values in current or related issues. Do more with issue links, project/user properties and send email. No need for groovy scripting.
Display any calculated value depending on other fields in current or linked issues, sub-tasks, epics, stories & JQL selected issues. Create highly configurable currency, duration and text read-only fields
More details
CUSTOM FIELDS
CONDITIONS & VALIDATORS
- Validation on Regexp
- Validation on Linked Issues/Subtasks/JQL Query
- Boolean Validator (Math, Date-Time, Text)
- Users in Field in - not in Project Roles
- Check Project Property
POST-FUNCTIONS
- Create Issues and Subtasks
- Copy a Parsed Text to a Field
- Math & Date-Time Expression Calculator
- Set a Field as a Function of Other Fields
- Add or Disable Options in Select List /Cascade Select List
- Assign to Project Role
- Parse Field for Extracting Data
- Format Field
- Add Comment
- Add-Remove Watcher
- Create / Break Issue Link
- Read / Write field on Linked Issues & Subtasks
- Read field from issues returned by JQL query or issue list
- Update issue fields
- Read / Set User Property
- Read / Set Project Property
- Transition Issues
- Log Work
- Send Email
More details
CUSTOM FIELDS
CONDITIONS & VALIDATORS
- Validation on Regexp
- Validation on Linked Issues/Subtasks/JQL Query
- Boolean Validator (Math, Date-Time, Text)
- Users in Field in - not in Project Roles
- Check Project Property
POST-FUNCTIONS
- Create Issues and Subtasks
- Copy a Parsed Text to a Field
- Math & Date-Time Expression Calculator
- Set a Field as a Function of Other Fields
- Add or Disable Options in Select List /Cascade Select List
- Assign to Project Role
- Parse Field for Extracting Data
- Format Field
- Add Comment
- Add-Remove Watcher
- Create / Break Issue Link
- Read / Write field on Linked Issues & Subtasks
- Read field from issues returned by JQL query or issue list
- Update issue fields
- Read / Set User Property
- Read / Set Project Property
- Transition Issues
- Log Work
- Send Email
Reviews for cloud
(111)Sign in to write a review
Hi Andrey,
Yes, you can extract the date and set field due date using "Parse field for extracting data" post-function.
Please, create an issue at http://support.decadis.net and I will explain you in detail the configuration needed to do it.
ADDED LATER: Issue #789
Thank you, Amy, for your review. I also generally prefer using validators than conditions, since they are more informative and less confusing. JWT also allows to present the users custom error messages in the language configured in their profile.
Some examples for boolean validations that can be implemented using JWT.
Anyway, sometimes conditions are invaluable, for example when we have parallel transitions (more than one transition with same origin and destination statuses), and we need to show only one of them, depending on field values, issue links, or any other issue characteristic.
Thank you, Lacey. You made my day.
Thank you, Aliaksei.
Thank you, Rjve, for your review.
Reviews for server
(111)Sign in to write a review
Great review, quick read, thank you so much!
All the best - your xApps team
Hi Emma,
you made our day! Feedback like this is what keeps us going. Keep the tricky questions coming - Max is ready!
All the best - your xApps team
Hi Mr. Hentschke,
thank you so much for the review!
All the best - your xApps team
Hi Antonia,
thank you so much for your review. This kind of feedback is what keeps us going!
If you like the product and the documentation so far, stay tuned! More updates are on the way!
All the best - your xApps team
Hi Neo,
thank you for an excellent product and support review.
All the best - your xApps team
Reviews for Data Center
(111)Sign in to write a reviewHi Andrey,
Yes, you can extract the date and set field due date using "Parse field for extracting data" post-function.
Please, create an issue at http://support.decadis.net and I will explain you in detail the configuration needed to do it.
ADDED LATER: Issue #789
Thank you, Amy, for your review. I also generally prefer using validators than conditions, since they are more informative and less confusing. JWT also allows to present the users custom error messages in the language configured in their profile.
Some examples for boolean validations that can be implemented using JWT.
Anyway, sometimes conditions are invaluable, for example when we have parallel transitions (more than one transition with same origin and destination statuses), and we need to show only one of them, depending on field values, issue links, or any other issue characteristic.
Thank you, Lacey. You made my day.
Thank you, Aliaksei.
Thank you, Rjve, for your review.
Cloud Pricing
Server Pricing
Data Center Pricing
| 10 users$10 | 25 users$80 | 50 users$160 | 100 users$320 | 250 users$750 | 500 & upAdditional pricing details |
| 50 users$250/year | 100 users$350/year | 250 users$750/year | 500 users$1,100/year | 750 users$1,400/year | 1000 & upAdditional pricing details |
Pricing FAQ
- How does server app pricing work?
Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for server apps?
For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are available for server apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Pricing FAQ
- How does Data Center app pricing work?
Data Center apps are sold as an annual subscription. You are eligible for support and version updates as long as your subscription is active.
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my Data Center pricing?
Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Can I install this app in a Data Center product?
Yes, this app has a Data Center approved version. If you're using a Data Center product, you should install the Data Center version of the app.
- What type of license do I need if I'm using this app in a Data Center product?
Because this app has a Data Center approved version, you should purchase a Data Center license for the app.
If you already own a server license for this app, you can continue using the server license in your Data Center product for a limited period of time.
- Do you offer academic, community, or open-source licenses for Data Center apps?
For Data Center apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.
Community and open-source licenses are not available for Data Center apps. Learn more about community and open source licenses.
- Can I extend my free trial?
For Data Center apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian product, and you're all set.
Decadis AG is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Decadis AG is a Top Vendor, committed to providing support for their apps at least 8 hours a day, 5 days a week.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Vendor support resources
Find out how this app works.
Atlassian-hosted discussions connect you to other customers who use this app.
Versions
Version 2.5.0 • Jira Server 7.3.0 - 8.1.0 • Released 2019-04-08
Summary
New feature: Move issues post function. And much more.
Details
New features
- Move issues on a transition using the Move issues post function
- Use advanced parsing mode for composing meaningful error messages in all validators
- Added the xApps Library to use our Expression Parser in several upcoming apps (Automation Toolbox for Jira being the first)
Improvements
- Reference standard objects like issue types, statuses or resolutions by ID, e.g. use status(1) instead of "Open"
- Use IDs for custom field options, e.g. use option(10001) instead of "Option A"
- Skip validations for issues being created by email
- Set the assignee to Automatic
- Mark all values in a multi-valued field as required in the A field is/isn't initialized or has/hasn't been modified validator
- Use Standard option for fields in the Create issues and sub-tasks post function
- Parse text for selecting transitions and statuses within the Transition issues post function
Bug fixes
- Several bug fixes
See the full release notes here.
Versions
Version 2.5.0 • Jira Data Center 7.3.0 - 8.1.0 • Released 2019-04-08
Summary
New feature: Move issues post function. And much more.
Details
New features
- Move issues on a transition using the Move issues post function
- Use advanced parsing mode for composing meaningful error messages in all validators
- Added the xApps Library to use our Expression Parser in several upcoming apps (Automation Toolbox for Jira being the first)
Improvements
- Reference standard objects like issue types, statuses or resolutions by ID, e.g. use status(1) instead of "Open"
- Use IDs for custom field options, e.g. use option(10001) instead of "Option A"
- Skip validations for issues being created by email
- Set the assignee to Automatic
- Mark all values in a multi-valued field as required in the A field is/isn't initialized or has/hasn't been modified validator
- Use Standard option for fields in the Create issues and sub-tasks post function
- Parse text for selecting transitions and statuses within the Transition issues post function
Bug fixes
- Several bug fixes
See the full release notes here.
Installation
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Jira Workflow Toolbox via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Jira Workflow Toolbox. You're prompted to log into MyAtlassian. Jira Workflow Toolbox begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Jira Workflow Toolbox versions compatible with your instance, you can look through our version history page.
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new apps or Find new add-ons from the left-hand side of the page.
- Locate Jira Workflow Toolbox via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Jira Workflow Toolbox. You're prompted to log into MyAtlassian. Jira Workflow Toolbox begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Jira Workflow Toolbox versions compatible with your instance, you can look through our version history page.
Similar apps
