Issue Summary

When you try to publish a rule that has an archived project under its scope, the application will prevent the rule from being published, presenting an error message stating the lack of permission on a project depending on the action. E.g. comment on issue action

• Error message: Either you or the rule actor for this rule is missing some required permissions: ADD_COMMENTS
  

But, the real problem is not simply the lack of permissions, the real problem is that the project is archived.

In case customers cannot find the offending project(s), they will need to reach our support for assistance.

Steps to Reproduce

• Create an Automation rule, adding two projects under its scope. Publish that rule
• Archive one of those projects
• Edit something on that same rule, and try to publish it again

Expected Results

The rule will not be published stating that one of the projects is archived, and will point to the project(s) that are archived.

Actual Results

Automation simply states the lack of permission.

Workaround

None at the moment.