I am trying to use the date fields (like {{now}}) to find the Month value (i.e. "Aug") to append to the beginning of the Summary field. I want to have an automation that will create work on a monthly schedule for the 1st of each month.
Hello @David Tieman
When you use the Edit Issue action set the Summary field to this value
{{now.format("LLL")}} {{issue.summary}}
The information about pulling the pieces (i.e. month) from a date field can be found in the details of the format command in this document.
https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#--
You have to follow the link to the Java documentation for more detailed information about the proper formatting.
Apologies for the additional message however, this doesn't appear to be working, as I am not seeing any change on editing the Summary field, no error received either.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please show us your complete automation rule and the details of the step where you are changing the Summary field.
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 have a typo in the smart value.
You have an extra "s" in there. Also the "i" needs to be lower case.
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.
I have this corrected now and the Summary is only showing the "Aug" value, it is not picking up and appending the previous value "CLONE - AUG: QA SAD Reload". :-(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So, you are not getting "Aug <the original summary in the issue>"? Or you are getting that but that isn't quite what you want?
If what you are getting is not exactly what you wanted, please provide an example of what the summary would look like before and what you want it to look like after.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The update is only providing the "Aug" text, I was hoping it would append the month, "Aug" to the front of the existing Summary text.
So for this test the existing Summary text is "CLONE - AUG: QA SAD Reload" (which I realize is a bit confusing to show CLONE) but the new Summary text would say "Aug CLONE - AUG: QA SAD Reload"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you show us the Edit Issue action details again please?
When I use the same code in my own automation rule it works exactly as you wish.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here is the Edit Issue step, also here is the Activity screenshot from the change completed by the Automation step. Because the initial example was getting confusing with the "CLONE" text in the Summary I moved to another issue I was testing with, so the summary content is slightly different. But the result is still the same.
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.
In your smart value it looks like you have a space between {{issue. and summary}}
If that is the case, that explains the problem. You need to remove that space.
Smart values can be very sensitive. You need to make sure you are using the right case, and have spaced only where they are supposed to be.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for your support and patience. This is working as expected.
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.