I have created a custom field, date picker, called "Public Release Date".
I have created an automation email that sends an email whenever that custom field is entered or edited.
But I do not know how to represent that new data in body of the email?
Help would be appreciated!
Thanks
There's also a Jira Automation Template Library available for help you can find it here.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you! So I have tried:
- {{issue.status}} which gave me Public Release Date: 10162 which isn't an actual date
- {{issue.duedate}} with no luck
- {{issue.[Custom Field].status}} just as a try but no luck
Any other suggestions?
Thanks,
Jamie
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately {{issue.[Custom Field].value}} didnt work either. Will review the link you sent! Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know this might sound silly but you did change Custom Field to your own name correct.
re:
{{issue.[Public Release Date].value}}
{{issue.[customfield_xxxxx].value}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not silly - is my first time anyway! I have tried:
{{issue.[Public Release Date].value}}
{{issue.[Public_Release_Date].value}}
{{issue.[PublicReleaseDate].value}}
But with no luck...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Have you tried the customfield_xxxxx you can find that information as per the link above "Find the smart value for a field"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes finding the JSON representation is a bit beyond me here... to open my relevant info, do I need to change the values below?... I want this field value automation to display whichever issue has been updated, not a specific issue. Does that make sense? Do I need to put:
- myinstanceurl???
- Issue key?
https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yes your instance and key
It won't be a specific issue after this information gathering :) we're just trying to get the custom field internal id rather than it's name re: customfield_12345
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
don't use the name and the id just the id exactly like this
{{issue.customfield_10058.value}}
also try
{{issue.customfield_10058}}
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.
Please try this without the [ ] in the statement as per my edit above.
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.
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.