Restriction to forms added by automation

[Ismael Rodrigues Martins]

Helllo!

Recently Atlassian released the restrict view to forms. It is a nice feature and helps to combine related context in the same request without breaking it in too many security levels. But theres a limitation: The features does not help much if you want a customer to submit the form and only a ceartain group of agents to view it. Here's my scenario:

I have a request type for reimbursement request that must be approved from a manager outside the financial team. Once approved, the customer must inform the bank information for payment. I wanted to attach the form for bank information after the approval step and restrict the view only to the financial team. But doing so with automation will make the user who run the automation be the "reporter" for the form, and preventing the original reporter from the trigger issue to submit the information.

I decided to go with a second request and with a security level applied, but it would be a lot easier if in the automation I get to set the reporter OR to check an option so the reporter is the same as the triger issue.

[Ismael Rodrigues Martins]

Hello John!

Actually the automation is not changing the reporter. The thing is that the actor of my automation is the user who triggered the rule; one of the steps in the automation is attach a form to the trigger issue. But once I set restriction to the form, the reporter (from the trigger issue) wont have access to the form because the access goes to the actor who triggered the automation.

In my case it makes sense the attached form appears for the reporter to edit only after the approval step, But beacause of this behavior I created a second automation only for the attach step that triggers when the issue is created, so the reporter can have access to the form.

[John Funk]

Hi Ismael - Welcome to the Atlassian Community!

Not completely following you on the Reporter part. Automation should not be changing the Reporter from the original submission. Can you share the Automation rule that you are using and what part is not working? 

[Ismael Rodrigues Martins]

Hi again John! Sorry, I messed up the text boxes and end up suggesting an aswer instead of answering to you. 

The automation works just fine, the thing is:

I set the automation to trigger upon issue creation to attach a form to the issue. I'm using the restriction view in the form. I wanted the issue reporter to have permission to edit the attached form. So I tried set the automation actor as "user who triggered the rule". But the automation fails the user does not have permission to attach a form, it seems. When I use the "Automation for Jira" as an actor the form is attached, but the issue reporter is not able to edit the form

I noticed that "Automation for jira" appears in the issue view on the list of user who can view the form (along with me and a group I set in the form restrictions feature)

Is there a way to add the reporter to the form restriction?

[John Funk]

Unfortunately, you can't use fields or project roles to grant access to view the form rigt now - it's a very manual thing.