Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,558,035
Community Members
 
Community Events
184
Community Groups

Automation: issue created in a different project with the parent project

image.png

 

Trying to create a new issue for an epic, but I want that issue in a different project. The problem is it won't associate the issue with the epic.

1 answer

1 accepted

0 votes
Answer accepted
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 22, 2023

Hi Daniel - Welcome to the Atlassian Community!

What is the trigger that causes this automation to fire? Is it something that happens with the Epic and you want to then create another issue (in a different project) with the trigger issue to be the parent? 

If that's the case then the Epic Link field should use:

{{triggerIssue.key}}

We used to trigger automation through components. I tried to trigger this one through the manual trigger trigger from within the epic. Ideally, I'm creating the epic and at some point, in time I want to create these tasks for the other project.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 22, 2023

It's really going to depend then on how it gets triggered. If you create the Epic and then want the children to get created immediately OR if a value changes on the Epic (field or status based on a transition), then the above code works. If it is something else, we would need more specifics. 

I'm going for the latter really. In which case I'm using the manual trigger. The problem is that the tasks aren't getting associated with the epic link.

Kelly Arrey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 22, 2023

How does the automation rule know which epic to associate the tasks with? 

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 22, 2023

Yep - that’s the question.

Like Kelly Arrey likes this

So that's my question. What can I do so the automation knows to associate that epic? I tried using {{issue.Epic Link}} and starting the automation from within the epic with the manual rules. Should I create a field that exists within that epic? I feel the issue is that the the new tasks are being created in a different project.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

So, can you lay out your scenario? What issue are you on when you do the manual execution? And what do you expect to happen? 

A project manager wants the epic to exist within their own project but wants the tasks to exist in multiple other projects. 

I don't want them to manually create the task, and it is something that repeats itself with every epic. I want to create automation to open tasks in different projects with specific fields and such. 

I expect the tasks to be opened with automation in the projects they need to be in + have the correct epic link.

John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

So the project manager is in an Epic, then clicks on the execution of a manual automation rule, and it creates the children stories identified in the rule (regardless of the project). Is that correct? 

If so, what I showed you above is what you should do for the Epic Link field in the children getting created. 

@John Funk It worked perfectly. Thank you so much. I didn't understand I needed to put it in the epic link. Much appriciated.

Like John Funk likes this
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 23, 2023

Great! You are very welcome. Sorry for not being more clear to begin with. 

Think nothing of it. You've helped immensely.

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events