Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
Teams
, (opens new window)
Create on Transition for Jira
Results will update as you type.
  • Cloud
  • Data Center
    • Overview - Data Center
    • Installation - Data Center
    • Getting started - Data Center
    • Use cases - Data Center
      • Copy a custom field value to another field - Data Center
      • Determine where COT functions are in use
      • Create a value map using the cascade select configuration
      • Pattern match condition
      • Prevent creating duplicate issues
      • Pattern substitutions for string manipulation
      • Set third party app custom fields while creating multiple issues
      • How are error messages generated during workflow transitions
      • Copy epic and its issues using the Create Issue post function
      • Create a linked issue in another project only if one doesn't already exist - Data Center
      • Create sub-tasks for specific issue types
      • Debug condition configurations
      • Copy attachments to a newly created issue
      • Create and link issue on exact summary match
      • Create issue if transitioned by specific user - Data Center
      • Create multiple issues - Data Center
      • Create multiple issues for each fix version - Data Center
      • Create subtasks on initial issue create
      • Add condition to a blank or an empty field
      • Retrieve problem determination information
      • Define condition based issue creation
      • Link newly created issues on transition
    • Features - Data Center
  • Migration
  • Release notes
  • Upcoming releases
  • Help and support
  • Appendix
    You‘re viewing this with anonymous access, so some content might be blocked.
    /
    Define condition based issue creation
    Updated Jun 27

    Define condition based issue creation

    This article explains how to allow the post function to only create the issue if certain conditions are met by the original issue. 

    Types of conditioning

    Subtask conditioning

    This has been available for many versions. It prevents the creation of subtask if the original issue is a subtask and the configuration says to not create a subtask in this case. It has the optional capability to create a subtask which is a sibling of the original issue.

    Example

    Pattern matching conditioning

    This takes advantage of the find/replace capabilities to provide a very flexible way to condition the creation based on matching issue information with a regex pattern. This may be a little bit more complex/less usable for simple cases, but can be very powerful for covering many use cases. The simple cases can still be done with little knowledge of regular expressions.

    All the standard substitution variables can be used. For instance, see the help text at the bottom of the add or edit screens.

    Refer to Pattern matching conditioning for more details.

    Example

    This example shows 2 simple conditions being used:

    • Project of the original issue must be ZCOT or no subtask is created.

    • Original issue type must be a Bug and its priority must be either Major or Critical or no subtask is created.

    Need support? Create a request with our support team.

    Copyright © 2005 - 2025 Appfire | All rights reserved.

    {"serverDuration": 26, "requestCorrelationId": "dc6897b3484540bc92a68700a330e472"}