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; } } }

automatically created task when specific task is present in a epic and epic status is change

Umar Maroof

Hi hope everyone is doing well

I want to create a rule where I want to create a task when the epic status is change but the condition is there must be a specific task present inside the epic so it can create the new task otherwise it cant i.e

If the epic transit from in progress to ready to Pulish then if epic have the task name tasks for backend developers then it will create a new task backend publish task

I construct the following rule but its not working Screenshot (21).png

Accepted answers

Fabian Lim

Hi @Umar Maroof

Can you share a screenshot of your audit log to see what the error is?

Regards

David Fischer

Hi @Umar Maroof ,

if you have JMWE, you can add a Create Issue(s) post function to your Epic transition (in the workflow editor), configure it to create the "Backend publishes task" (it should be fairly straightforward), check the "Run this post-function only if a condition is verified" option at the bottom of the screen and provide a "condition" like this:

{{ issue | stories("issuetype") | filter(["fields.issuetype.name","Tasks for backend developers"]) | length > 0}}

Let me know if you need more help.

All comments

Fabian Lim

Hi @Umar Maroof

Can you share a screenshot of your audit log to see what the error is?

Regards

The rule doesn't work because you are looking for a parent for the epic which does not exist. So that's why is empty.

You can try creating a branch to go under the tickets in the epic (https://support.atlassian.com/cloud-automation/docs/what-is-rule-branching/)

Then use a JQL condition to check whether the specific ticket type and summary exists, if it does, then you can create a new variable action that tells you that the ticket exists.

Branch out of the rule and then transition the epic and create a new task and link it.

If you have the budget, I would spend the money on JMWE or JSU which have workflow functions pre-built for this. This action for Jira Automation becomes very messy.

Regards

Umar Maroof

@Fabian Lim I have JMWE, but I am not sure how to achieve this by JMWE.

David Fischer

Hi @Umar Maroof ,

{{ issue | stories("issuetype") | filter(["fields.issuetype.name","Tasks for backend developers"]) | length > 0}}

Let me know if you need more help.

Umar Maroof

@David Fischer I copy the same condition that you give me still its not working Screenshot (23).png

David Fischer

Please note that the issue type name is case-sensitive. Can you check the exact issue type name of the issue that should be under the Epic being transitioned for the new issue to be created?

Umar Maroof

@David Fischer see the name is same Screenshot (24).png

Welcome!

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

Quick Links

Unanswered
Groups
Help

Find more posts tagged with

cloud

jira-software

jira-software-cloud