Clonar reglas de automatización de jira a otro proyecto

[Claudia González]

Hola, 

Estoy usando la aplicación Deep Clone For Jira. Ya pude clonar mi proyecto con todas las incidencias, ahora bien, me gustaría saber si es posible clonar las reglas automatizadas que cree para el proyecto de origen, clonarlas hacia el proyecto clonado. Me sería de mucha ayuda lograr clonar esas reglas.

Desde ya muchas gracias

Saludos. 

[Nic Brough -Adaptavist- · Accepted solution]

In point 1, there's a slight hitch - all new users will be added to the "contractors" group automatically now.  But other than that, it's correct.

2.  No.  You have to explicitly say that a role, group, user or other thing can see issues in a project, and then they get to see all of them.

However, if you use "issue security", you can set it on an issue-by-issue basis

[Shayne _Atlassian_]

You can grant Browse Project permission to the groups you'd like to allow to open issues between projects. For example, if the Marketing team needs to open issues from the IT Project, you'd change the IT Project's permission scheme by adding the 'Marketing Group' to the Browse Project permission. 

This would allow the 'Marketing Group' to open all issues in the IT Project; it does not control individual issue access.

 Managing Project Permissions has more information on this option.

You may also want to look into issue-level security. From that page:

Issue security levels allow you to control who can see individual issues within a project (subject to the project's permissions).

Why use issue security levels?

As an example, a company may have a public instance of JIRA running. Within this instance they may have several projects that external people (customers) can browse. However, it may not be appropriate to show all issues to the customers.

[Miroslav Brabenec]

Perfect. I used Browse Project permission for Custom Field which is Group Picker (multiple groups) type and it works!