@Anthony -
Welcome to the community. Please provide the error that you are receiving when your automation rule executed, so we can review and advise further.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Technology Applications Team
Viasat Inc.
Hi @Joseph Chung Yin
The error message is as follows:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Anthony -
Can you confirm if you disable the rule and are able to access all the fields in question via the project UI of the issue - to manually update those fields?
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Joseph Chung Yin
Yes, at the moment I disabled the rule because I couldn't make it work.
I tested and can update all fields manually through the project interface.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Anthony -
Can you provide your "Edit issue field" action details (example - "Plataforma" field) and how/what you want to update the field? Example - How are defining the value to be used in the update? Since it seems you already configured Jira/JSM custom fields which sourced/mapped to the Assets schema.
Secondly, who is the rule actor of your automation rule? Does the actor have edit/access rights against your Assets schema?
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I removed Automation for Jira and added my user who has full permission to Assets and it didn't work either, follow the automation context and some more screenshots
I have a JSM Portal form that contains a field called pre-approved template.
In other words, when the user chooses a template, in my case "MAIS UM TESTE 6", the Plataforma, Origem da Mudança, Ambiente and Fornecedor fields must be updated in the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Anthony -
Can you change your smart value syntax of {{issue.customfield_15294.Plataforma}} by removing ".Plataforma" at the end? I am assuming that this customfield has already been defined/sourced from your Assets schema object type named Plataforma?
Best, Joseph
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.