I keep on running into permissions issues with enabling rules for some projects in particular. I checked the permission scheme and `atlassian-addons-project-access` does have Administer Project rights (in the Project Role). I am also an admin for this instance, so I should have all permissions as well.
I'm reaching out to see if others have run into this issue before and if so, how did you resolve it?
After further investigation and help from Atlassian Support, we discovered that the error preventing me from adding that specific project to the global rule was not due to permissions issues, but it was because a recently archived project was still in the scope for that particular rule.
Once I removed the archived project from the scope, I was able to add additional projects to that global rule without error.
There will be a feature request created from Atlassian's side to improve the error message in the future should anyone else run into this issue.
"atlassian-addons-project-access" has been applied to all permissions in that scheme, but still no luck.
I ended up creating a support ticket and upon further investigation, I believe it may have to do with the project linking out to other projects/ boards where "atlassian-addons-project-access" may not have permissions. However, I'm still scratching my head on this issue as it hasn't occurred before and 15 other projects are using this rule.
Hi Everyone, In this roundup we combine all the jira automation rules to sum up story points across different issue types. We start from the lowest level, summing up story points from sub-tasks t...