Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation: Create Linked ticket in another project

I am trying to set up an automation rule (global) that accomplishes the following:

  • When an issue in ProjectA (only) transitions from Backlog to Selected for Development
    • Create a new ticket in ProjectB, and link them via created/creates link type, and set its status to ProjectB's Selected for Development status

And then a secondary automation:

  • When the linked issue in ProjectB updates from Selected for Development to In progress, update the status of the linked ProjectA ticket.

 

For the first automation, here is what I tried to set up:

  • When Issue Transitioned from Backlog to Selected for Development
  • For Current Issue
    • Create a new issue of same type in ProjectB
    • And: Link issue to: Most recently created issue

Audit log is showing these two errors:

  • Could not find create meta data for project/typeId #####/#####
  • Error linking issues: At least one of 'id' or 'key' is required to identify an issue

 

This rule was set up with the scope set to both of the projects.

Both projects are company-managed; Both projects are using the same scheme and workflow as well.

2 answers

1 accepted

1 vote
Answer accepted
Tansu Akdeniz Community Leader Apr 14, 2021

Hi @Eric Van Pyrz 

Can you please verify the existence of the fields for the creation in target Project B? There might be a config change. 

Please attach a screenshot from the automation if possible.

Best

Hey @Tansu Akdeniz , screenshot attached below, with the create issue option open. Both projects should have identical fields and issue types, since they share the same scheme and workflow. Additionally, both projects have the same component and release versions listed, too.

 

2021-04-15_22-38-33.png

Tansu Akdeniz Community Leader Apr 15, 2021

You said projects are identical but I want to be sure.

Please check;

  • The existence of same issue type and priority in MNG project.
  • All those fields availability in MNG project create screen.
  • Validations and required fields in MNG project for creation.

If everything seems fine, can you please only send summary and description as a parameter and remove other fields (if not required in MNG) in automation ?

1 vote
avo Atlassian Team Apr 19, 2021

Hey @Eric Van Pyrz 

This worked for me:

Screen Shot 2021-04-20 at 3.10.20 pm.png

In addition to what @Tansu Akdeniz suggested, something to look out for as well is are both projects classic or next-gen projects?

Hope you work it out!

Suggest an answer

Log in or Sign up to answer
TAGS

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you