Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-401

Team Managed Projects: When an issue on Next-Gen (TMP) has group restrictions, automation fails to execute for lacking permissions for the Actor

XMLWordPrintable

    • Minor
    • 0

      Issue Summary

      When the user changes restriction roles to any ticket, automation fails to trigger transition rules. due missing permissions from actor (addon_com.codebarrel.addons.automation

      addon_com.codebarrel.addons.automation user is not able to read issues that are restricted to other roles where this user is not assigned (by default is assigned to atlassian-addons-project-access role), you cannot add roles to this user, because security groups or the user itself is not assignable.

      Steps to Reproduce

      1. Create an automation rule that is triggered in any transition.
      2. Create an issue.
      3. Change restrictions to the Administrator role only.
      4. Transition this issue.
      5. Automation rule must fail due to a lack of permissions on Actor.

      Expected Results

      Rule Execution

      Actual Results

      Actor does not have permission to view one or more issues, or the issue was deleted (please check permissions and issue security levels):
      Comment (id:10134) for issue NGS-1 (id:10163)

      Workaround

      Change the rule actor to a user that has permission.

            [AUTO-401] Team Managed Projects: When an issue on Next-Gen (TMP) has group restrictions, automation fails to execute for lacking permissions for the Actor

            Jeroen van Winden added a comment - - edited

            Regarding the workaround: the only option is to set another JIRA user as the actor. Although this fixes the permissions issue, this can cause confusion as the automation actions will appear as if it was a manual action from a user. For example: "User A has transitioned this issue from in progress to done".

            A second workaround for that is to invite a dedicated new user to the organisation, call it 'Jira automation' and assign that as the Actor. So at least it will be clear it was an automation rule. This will however cost a dedicated Jira seat, so a fix from Jira is still very much desired (or a free Jira seat )

            Jeroen van Winden added a comment - - edited Regarding the workaround: the only option is to set another JIRA user as the actor. Although this fixes the permissions issue, this can cause confusion as the automation actions will appear as if it was a manual action from a user. For example: "User A has transitioned this issue from in progress to done ". A second workaround for that is to invite a dedicated new user to the organisation, call it 'Jira automation' and assign that as the Actor. So at least it will be clear it was an automation rule. This will however cost a dedicated Jira seat, so a fix from Jira is still very much desired (or a free Jira seat )

            Ignacio Pulgar added a comment -

            A similar issue may occur in company-managed projects which workflow contained status properties which restricted permissions.

            Maybe an Automation Rule could be set to ignore status properties?

            Ignacio Pulgar added a comment - A similar issue may occur in company-managed projects which workflow contained status properties which restricted permissions. Maybe an Automation Rule could be set to ignore status properties?

              Unassigned Unassigned
              4a7d33d40182 Cesar Arzate (Inactive)
              Affected customers:
              15 This affects my team
              Watchers:
              30 Start watching this issue

                Created:
                Updated: