Why clone automation is not available in team managed projects

[rakshita malik]

If 2 projects are team managed then clone automation is not working, however it is available in company managed projects. Need to provide this functionality in team managed projects as well

[Bill Sheboy]

Hi @rakshita malik 

What do you mean by "is not working"?

If you have a rule which does not work as expected, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

As @John Funk described, team-managed projects are independent of one another.  Cloning issues within a single project will work...if the fields, issue types, etc. are not confused with ones in other projects.  The work-around for those symptoms is often to use the custom field id, or other id values, with JSON edits to specifically set the correct values.  Cloning between projects could have the same concerns / limitations.

Kind regards,
Bill

[John Funk]

Hi Rakshita,

Not exactly sure of your question, but Team-managed projects by design are to be completely independent of all other projects. So if you are trying to clone something from one project to another, that's probably why it is not available like it is for Company-managed projects. 

If you need that functionality, you should use Company-managed projects instead.