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.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.