Problem creating a new ticket in another project maybe caused by using different products?

Question

Hello

I've scanned through the community and found some similar questions but was not able to narrow it down to what I'm currently encountering.

I try to run a global rule to create a ticket of the same type in another project (SCMF) when a new ticket is created in the original project (SMS). The rule is fairly straight forward:

- Create the new ticket with the same type in the other project

- update some of the fields

- link the two issues

- send an info mail so a person can manually edit the newly created ticket

Now when I create a ticket in SMS, the rule creates an error, according to the auditlog, as follows:

I checked the project ID 10446 and it corresponds to the SMCF project. And I am sure that within SCMF, I do have the corresponding issue types (tried it with Task, Bug but neither worked).

The only thing I could think of now is that the two projects are not identical in terms of project type:

* SCMF is a company managed software project
* SMS is a team managed business project

Could it be that they cannot be connected using this automation rule? I'm quite sure that I do have the right admin role to implement this rule.

Any hints are highly appreciated

Reto Gantenbein · Answer

Thank you @Valerie Knapp

It was just proven that it works as the rule was invoked from another project (side effect, not intended...) that is company managed so yes, the problem must be in the fact that I try to perform this rule between two different types of projects.

So I guess I have to create a new company managed project for SMS and then it should work.

Thank you for your help

Valerie Knapp_dpp5c6 · Answer

Hi @Reto Gantenbein , welcome to the Atlassian Community and thanks for your question.

You have answered yourself here

* SCMF is a company managed software project
* SMS is a team managed business project

The issue types in a team-managed project are not the same as the company-managed project, so this is likely the reason you are getting the error.

Can you try, instead, of putting the same issue type to see if you can map onto the team-managed issue type?

I don't have a lot of experience getting this type of rule to work but you've come to the right place to ask for help.

Best wishes