How to fix automation attachment form error?

[Amarillas Erika]

I've been having trouble with my automation
There are two request type with the same status, I am using an if-else case to automate the attaching of different form.



I am using this condition:

When status = Waiting for requester

If Request type = A
     Then attach form A

Else if Request type = B
    Then attach form B

Sometimes it would work then the next day it gives this error. Please tell me what causes this.

[Judd Garratt - Path of Trees · Accepted solution]

Hi Amarillas,

It's tough to say for sure what is causing the error, but here are two things you can try:

• Change the rule actor to a user with Jira admin permissions and see if the error goes away. If it does, then atlassian-addons-project-access in your project's permission scheme (which controls the permissions for the default automation user) is probably missing a permission to do one branch of the rule's actions.
• If nothing changes, try looking at issue security settings to make sure that the rule actor has permission for any issues that might have issue security applied.

Good luck!

[Amarillas Erika]

Thanks for this! You were right. It was the rule actor condition that caused the error. Thank you!

[Judd Garratt - Path of Trees]

No worries, glad to help :)

[Amarillas Erika]

Any chances, you know how to add a property key and property value in transition?

If I want to pre-configure the default value or urgency or priority when transitioning into a status, how do I modify the property key and value of that?
Do you have any syntax?

[Judd Garratt - Path of Trees]

My apologies @Amarillas Erika, I missed your message.

There are a couple ways you could achieve this. One is with automation itself.

(1) With automation

• Add a new rule, with 'Issue transitioned' as the trigger.
• Set whichever from/to status you need
• Select 'Edit issue fields' as the action
• Pick one or more fields and set the value you need (e.g. priority = high)

When the rule runs, it will edit those field values on the transition you set.

(2) With a workflow post-function

• Edit the workflow for your project. You can quickly find this by going into Project settings, selecting Workflows and then clicking the pencil icon under 'actions' in the table.
• In 'diagram' mode (you can toggle this on in the top left if it doesn't show by default), click the transition you want to configure (arrow line pointing into a status). Then in the white box which pops up, click 'Post-Functions' in the list of links.
• One the post-functions page, click 'Add a post function'.
• In the long list that comes up next, select 'Update issue field'. Select the field from the list, pick the target value and click 'Add'.
• If you don't see the field you're after in the list, go back a step and select 'Update issue custom field' in the long list of radio options.
• To edit multiple fields, just create multiple post-functions.

When an issue follows the transition you just edited, this post-function will run and modify the field values you set.

For simple field edits on a transition, post-functions are a good choice because they don't count towards automation quotas. If you need more complex evaluation or open-ended triggers (e.g. any transition into X status), then automation is the way to go.