Hi Everyone, I'm having difficulties starting this automation, looks like I was only able to create sub-tasks with a defined number but I need the following: In Project 1: * When a user creates an Epic and custom field has at least 1 value selected * A task must be created within that epic. For example: Multiple Selection * Iaas * Saas * Paas - User selects Iaas and Saas, 2 tasks will be created under the parent Epic with Title "Iaas' for example according to the selection. Thank you,

Hi @Christian Delgado You can do it with something like this: * TRIGGER: Issue Created * CONDITION: Issue Type = Epic * BRANCH (Advanced): {{issue.YOURCUSTOMFIELD}}* ACTION: Create Issue (Make sure to set the Epic Link to {{triggerIssue}})

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Simple Automation Question

Christian Delgado

Hi Everyone,

I'm having difficulties starting this automation, looks like I was only able to create sub-tasks with a defined number but I need the following:

In Project 1:

When a user creates an Epic and custom field has at least 1 value selected
A task must be created within that epic.

For example:

Multiple Selection

* Iaas

* Saas

* Paas

- User selects Iaas and Saas, 2 tasks will be created under the parent Epic with Title "Iaas' for example according to the selection.

Thank you,

Accepted answers

Mark Segall

Hi @Christian Delgado

You can do it with something like this:

TRIGGER: Issue Created
CONDITION: Issue Type = Epic
BRANCH (Advanced): {{issue.YOURCUSTOMFIELD}}
- ACTION: Create Issue
  (Make sure to set the Epic Link to {{triggerIssue}})

All comments

Mark Segall

Hi @Christian Delgado

You can do it with something like this:

TRIGGER: Issue Created
CONDITION: Issue Type = Epic
BRANCH (Advanced): {{issue.YOURCUSTOMFIELD}}
- ACTION: Create Issue
  (Make sure to set the Epic Link to {{triggerIssue}})

Christian Delgado

This is what I have so far, this creates a task(s) within the Epic successfully, but it doesn't pull the name of the selection.

EXAMPLE:

TASK - Instead of TASK I want it the name to be Iaas

TASK - Instead of TASK I want it the name to be Paas

Mark Segall

You should be able to apply {{test}} to the summary of the created task to get the current custom field value it is iterating against.

Christian Delgado

This worked perfectly, thank you so much!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management