Hi @Paul Dokken
What is the problem you are trying to solve by doing this? Couldn't you just reference the Summary field later rather than duplicating the information...or...are you expecting the two fields will be updated independently later? Thanks!
Kind regards,
Bill
What we are trying to accomplish is have a field that we can display on a list displayed to our users from the app. We would start with the issue summary and then modify it to something meaningful to the user. If there is a better way of doing this I would like to know.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Paul Dokken - So you're just trying to copy the summary to a custom field called "Release Notes"? That would look something like this:
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.