Multiple 'atlassian-addons-project-access' causing Automation Failure

[Naman Batra]

Hi All,

We did cloud to cloud migration of two separate Jira instance into one single instance. After migration, we moved the automation rules via export/import.

Most of the automation were not working because the Rule Actor did not have permission.

On further investigating, we found that we have two Project Roles in System->Security->Project Rules:

• atlassian-addons-project-acces
• atlassian-addons-project-acces(migrated)

But in the project permissions we see only 'atlassian-addons-project-access (migrated)'

This is causing an issue enabling and using add-ons.

Is there anyway to fix this without manually going and updating each Permission Scheme/Permission/Role?

Additional info: 'atlassian-addons-project-access' is only linked to Default Permission scheme while the migrated role is linked to all other project specific schemes.

[Walter Buggenhout]

Hi @Naman Batra,

This is an unfortunate side-effect of how migration works. Atlassian's migration assistant uses a conservative approach to migrating data and configuration. When it finds something with the same name in the target site of the migration, it creates a duplicate item with - as you correctly observed - the (migration) appendix behind it.

For a clean and properly functioning site, I would indeed strongly recommend you to update all your settings and consolidate to one  atlassian-addons-project-acces item.

You can either replace the migrated one by the original in the permission scheme(s) where it occurs or link your migrated projects to a permission scheme that already was in your site. Also make sure that your automation rules are using the correct actor.

Hope this helps!

[Naman Batra]

@Walter Buggenhout Thanks for your input!

I have close to 28 Permission schemes with close to 30 roles in each. If I have to update manually, it will take a lot of time.

Do you know if Atlassian provides any API to do it easily?