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

Simply automation error



automation_jira.PNG

When trying to implement a simple rule an error like this in the print appears. Any idea how to solve it? I tried change everything in the automation rule, but the error continues.

Create issue

Could not find create meta data for project/typeId -10020/10147

 

3 answers

@bruno_vidigal - Did you get this resolved? 

I'm trying out a similar logic, but running into deadends. Let me know, please.

P.S., Re-fetch also doesn't yield results.

Bill Sheboy
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.
Apr 01, 2022

Hi @Shankar Giridhar Vijayakumar  -- Welcome to the Atlassian Community!

To get the most people seeing your question: I recommend creating a new question, linking to this thread, adding images of your automation rule and the audit log details showing an execution that does not work as you expected, and explain the problem you are trying to solve.  That information will provide context for the community to try to help.  Thanks!

Kind regards,
Bill

0 votes
frother
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Aug 24, 2020

Hi Bruno, 

Thanks for reaching out.

I think what is happening is that the issue type of the issue that triggered the rule doesn't exist in the Jarvis project.

It could even be that there are 2 issue types with the same name, which would also cause this problem. Are any of these projects nextgen projects? 

Thanks,
Scott.

0 votes
Bill Sheboy
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.
Aug 17, 2020

Hi @bruno_vidigal -- Welcome to the Atlassian Community!

I suspect you are running into a timing issue for the create issue trigger.  That is, the issue is not fully available to the rule logic at the time the trigger catches the new-issue event.

I have worked around this condition before by putting a Re-fetch action immediately after the trigger.  That will make the rule run a bit slower, and it will confirm the issue is fully loaded before accessing the fields.

Best regards,

Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events