Skip to main content
Skip table of contents

Setting the Parent Field After Issue Creation

šŸ’” Workaround: Setting the Parent Field After Issue Creation

At the moment, the Parent field isn’t supported directly during issue creation using native Jira Create Issue flow. This means you can’t preconfigure the Parent issue when setting up your template.

But there’s a simple workaround using Jira Automation.


āœ… How to Set the Parent Field Automatically

You can create an automation rule that updates the Parent field after the issue is created. The rule will check which template was used, evaluating ā€œTemplateā€ custom field, and if it matches a specific one, it will set the desired parent issue.

Here’s how to configure the rule:

  1. Trigger: Issue (work item) created

  2. Condition: {{smart values}} condition

    1. First value: {{issue.customfield_XXXXX.templateName}} ←-- put ā€œTemplateā€ custom field ID

      1. Learn how to get a Custom Field ID here

    2. Condition: equals

    3. Second Value: "Your Template Name"

  3. Action: Edit issue fields → set the Parent field key using a JSON snippet

CODE
{
  "fields": {
    "parent": {
      "key": "KAN-4849"
    }
  }
}

šŸ“ø Example setup:

image-20250408-115505.png
image-20250408-115537.png


If you'd like help setting this up or want to automate this further, reach out to us - we’re happy to guide you!

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.