Hi @Rodrigo diaz , thanks for your question.
Please can you give an example of what you hope to achieve?
It should be possible with automation, for example, on the creation of an issue to transform a custom field value entered by a user into another custom field value.
I always recommend that people take a look at the Jira automation template library, I found a rule that you could amend and test to see if you can get your desired outcome -
https://www.atlassian.com/software/jira/automation-template-library#/rule/1357059
Please take a look and give us your feedback if this helps you.
Cheers
I have achieved something similar using Structure and Automation. Your end users can see the custom field as " Masked Field Name" in the structure and it will always point to the custom field behind it.
If you expect your end users to change the value of the field, ensure they have right access level to edit via structure.
Also the custom field must be managable via structure and available on EPIC or Story template.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.