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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Having one project create an issue in another project (dynamically)


We have a Lead Generation Project in JIRA that we use to track software projects as they move through the pipeline. Each issue that moves through the board represents the 'brief' and references to everything across our business - especially finance. The issue in this project has a system field that allows a 'destination project' to be selected.  Sales and Project Managers live here. 

We manage the execution of that work in separate projects. We use Epics in the roadmap to map back to the issue in the Lead Generation Project. And Project Managers, Developers and QA live here. 

When an issue transitions in the Lead Generation Project to a certain status I need to create an epic in the 'destination project' based on the data provided in the Lead Generation Issue. This technically authorizes a small development project to start and have the ability to log time. 

Doing this manually is error prone, and allows people to work outside of the business procedures. 

Everything I can see in Automation allows me to pre-define the destination project, but since we have a lot of activity that requires everything to be kept separate due to conflicts, it needs to be driven by the data the issue has - the user selected destination project.  

Is this possible? 

PS. Trying to avoid a plug in and additional cost at the same time :)

1 answer

1 accepted

2 votes
Answer accepted
Darryl Lee Community Leader May 07, 2021

So the UI is a little wiggy, but when you have a Create issue action you can actually type  in the Smart Value in the Project field:

(If your field is a select field, you might need to use {{issue."Destination Project".value}})


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events