Skip to main content
All CollectionsSalto for JiraTroubleshootingDeploy Preview Errors
Can't deploy a non-global automation without projects
Can't deploy a non-global automation without projects
Scott Dixon avatar
Written by Scott Dixon
Updated over a month ago
Cannot deploy automation without projects.

In order to deploy an automation it must be either global, assigned to at least one project type, or assigned to at least one project that exist in the current environment.

What triggers this error?

This pre-deploy error is triggered when the deployment plan includes an automation rule that is both:

  1. Non-global

  2. Not associated with at least 1 project

All automation rules in Jira must be either global or scoped to at least 1 project.

How can I solve this?

If you intended to deploy this automation scoped to at least 1 project, go Back to Selection and choose the related project under Additional Dependencies to add the project to the deployment plan.

If you selected some projects, they may have been removed from the automation list if they don't exist in the target environment. You should include projects that either exist in the target environment, or new projects which were also selected for deployment.

Did this answer your question?