I am getting an error when I try to do a rule automation

eibokette
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 27, 2022

I have a simple rule automation that should create a new issue in a new next-gen project (x) when i transition another issue in project (y) to a new column on the board.

Screen Shot 2022-01-27 at 14.17.36.png

I have ensured both projects have the same columns, same issue types and same fields for each issue type.

However, whenever the rule runs I am getting this error in the audit log - 

Could not find create meta data for project/typeId - 11092/10466
Please is there anything I am doing wrong? Has any one has this issue before? how did you solve it?

2 answers

0 votes
Colton.Kosicek
Contributor
January 27, 2022

It looks like you are trying to run a multiple project command (aka rule triggers in project A and project B issues are changed).  If so you need Full Jira admin rights - unfortunately Atlassian hasn't enabled a specific role or privilege's to give to others yet to make global automations. 

 

Also keep in mind that any multi project or global rules go against your companies automation rule "limit".  Depending which tier of Jira you have will tell you how many total or how many per user you have as a company.

0 votes
Fabian Lim
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 27, 2022

Hi @eibokette

Are you creating this rule in the global administration settings? It touches multiple projects.

Regards

eibokette
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 27, 2022

@Fabian Lim no, I am creating it under Project Rules.

 

I saw this recommendation which I tried and it worked (so basically I am creating all of them now as Stories). But this is not ideal, as I will prefer the created issue retains the same issue type as the one that triggered the creation

Screen Shot 2022-01-27 at 14.41.07.png

 

I can also confirm that both projects have the same issue types.

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.
January 27, 2022

Hi @eibokette 

I believe create (and clone) issue actions are exceptions to the multi-project requirement noted, so no problem there.

Would you please post an image of your audit log details for the execution showing the error?  That may provide more context for what is happening.  Thanks!

Kind regards,
Bill

Like Colton.Kosicek likes this

Suggest an answer

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

Atlassian Community Events