Edit Permissions for Each Rule!

[Darryl Lee]

Oh hey, one of the concerns with using the Web Request action is that if your request requires authentication, then your password or token is visible to all Jira Administrators and more troubling, to Project Administrators (who maybe only needed that permission to add/manage Versions or Components/Leads.)

The issue (specifically pertaining to the Jira API, but it applies to any web request that requires credentials) was documented well by @Wolfgang Landes here:

• Is it possible to access Jira API via Automation for Jira without exposing credentials? 

In response, @bmccoy did create AUT-2117 which is still open, but it looks like  Atlassian may have provided something of a workaround:

Well, that's new! So cool. If you can't obscure the tokens/passwords for web requests, at least you can limit who can view/edit those rules. Good stuff Atlassian. Now can you please put it in the Release Notes?

And yes, why I do subscribe to the Atlassian Cloud Documentation blog and did not see this mentioned anywhere. Thanks for asking! :-}

[Taranjeet Singh]

That's a really cool and useful feature for Automation for Jira! Great work, Atlassian!

Thanks for sharing, @Darryl Lee !

I have a couple of follow-up questions, if you could provide some insights:

1. Does this new rule edit permissions feature applies to both project and global/multi-project rules or only global/multi-project rules?

2. Would this feature not impact a Jira admin's ability to edit any type of automation rules (if they are not provided edit permissions), project or global/multi-project rules?