Using epic name in a subtask custom field

[Douglas Oliveira]

Hi everyone,

I have the following structure Epico -> Task -> Subtask, I have a rule that when creating an epico standard tasks and subtasks are created together.
I have a custom field in the subtask with the name "Project", I would like that when creating an epic this custom field has the same name as the Epic Name.

Thanks!

[Mark Segall · Accepted solution]

Hi @Douglas Oliveira - In your rule that creates the sub-tasks, you can use this smart value to apply the Epic Name:

{{issue.parent.Epic Name}}

[Douglas Oliveira]

Hi @Mark Segall , 

I already used this smatvalue but it didn't work, I did it as follows

[Mark Segall]

I'm an English speaker so please confirm my understanding...

Based upon your screenshot, it looks like when an Epic is created, you're branching into sub-tasks and editing the items.

If my understanding is correctly, this is not going to work because when you create an epic, it will not yet have any tasks/sub-tasks yet.  I would recommend that you configure a rule like this:

• TRIGGER: Issue Created
• CONDITION: Issue Type = Sub-Task
• ACTION: Edit Issue (Project)
  • {{issue.parent.parent.Epic Name}}

[Douglas Oliveira]

Yes, that's exactly it, but that rule you gave me didn't work, I've tried replacing it with: {{issue.parent.Epic Link}}, it didn't work either.

[Mark Segall]

Sorry it should be this (just validated in my test environment):

{{issue.parent.epic.Epic Name}}

[Douglas Oliveira]

Hi @Mark Segall 

still not working, no action is performed when creating the epic.

[Mark Segall]

The "no actions performed" tells me that it's triggering, but not passing the condition so it is not recognizing that the trigger issue is a sub-task (you'll be able to confirm this by expanding one of those audit log entries).

I can confirm this works in my test environment.  

Lastly, to confirm my understanding, you are creating these sub-tasks manually.  If that's correct, the rule looks properly configured.  However, if you have another rule generating the sub-tasks, you'll need to make sure Allow Rule Trigger is checked on the Rule Details screen.

I hope this helps.

[Douglas Oliveira]

@Mark Segall 

I actually ended up forgetting to check the option to allow a rule to trigger the other. Now it worked fine!

Thanks!