Optional rules - Cloud

 

Description

Create Issue, Update Issues, and Create Subtask post functions can be configured to create or update the issue only if certain conditions have been met by the issue that is in transition.

Conditions

Define the conditions under which to create the new issue(s) or subtask(s) or update existing issue(s) or subtask(s). If these conditions are not met, then no issues or subtasks are created or updated. If you do not define any conditions, then your issues and subtasks are always created when the associated workflow transition occurs. There are two types of conditioning:

  • Subtask conditioning - prevents the creation of subtasks if the original issue is a subtask and the configuration indicates not to create a subtask. It has the optional capability to create a subtask which is a sibling of the original issue.

  • Pattern matching conditioning - takes advantage of the find/replace capabilities to provide a very flexible way to condition issue creation based on matching issue information with a regex pattern. Although this is a more complex configuration, it is highly powerful and covers a great number of use cases.

Configuration

Define additional configurations for the issues or subtasks being created or updated.

 



Find answers from the community.

Ask a question to the community.

Log a request with our support team.


Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2022 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.