Darryl Lee Community Champion

Hi @Julian Petrich - How are you creating your list of "distinctAssignees"? Because as far as I know that is not something you can get from a JQL lookup. The other problem is that even if you had a way to create a list (manually using split()? API call?), the problem is you cannot reference a Smart value from inside of a…

Ah, I forgot you were using Affected Services which is a special field from Insight so yeah, you need to use the replace() function like I did before, haha. So glad you figured it out.

Hi @Darren Nicas -- I was going to write something like what @Bill Sheboy wrote, but not as eloquently. :-} I was thinking about the 2nd case though, and it is kind of odd that even though each edit action runs asynchronously, it seems highly unlikely to me that they'd run in exact sync, and since the JSON you're using is…

Oh @Agraj Mangal makes a good point that you can limit who can run a manual rule. And also has some good points about securing your API token.

Hi @Saira - no, anyone can run the Automation, but you need to understand that any actions it takes will look like they are performed by YOU. It's good practice to create a Service Account (for example "Jira Automation") and use that to generate an API token to use, so that when users look at the history of a ticket, it is…

Hi @Saira -- It would be helpful if you can include screenshot of your current automation rule so we can see what you are doing now. If you are already using the Lookup issues trigger, then you can specify in the JQL summary ~ abc If for some reason you are doing a secondary Lookup issues, can you explain why? One thing…

So that's the right query. I think the next step is to "save" these counts somewhere if you are looking to see trends. Minimally, you could use a Scheduled Trigger to: * Do a Lookup issues on the above query * Then send yourself an email every day at the given time. You would include the count in the message with something…

AH, I did not know you were trying to modify the time captured from the summary, as in your original post you were using {{now.minusMinutes(30).format("HH:mm:ss")}}. Glad you figured it out. In your final solution, does {{summary.match...}} work or did you mean to write {{issue.summary...}?

OK, tested, and it looks like we have a winner: {{fieldChange.field}} I hope this works for you! Also, it's important to note this limitation: When there are multiple fields that have changed, {{fieldChange}} only contains the first changed value. If multiple values are changed, use # to iterate over these. For example,…

Thank you! I would try: {{fieldChange.fieldName}} {{fieldChange.field}} {{fieldChange.name}} (Weirdly on my test instance, I cannot even get {{fieldChange.toString or fromString}} to show me anything.)

Ugh, that's a lot of work. @mgouirand is monitoring at least 15 fields. :-/

Hi @mgouirand - it would be helpful if you can provide a screenshot of your actual Automation Rule or the comment/notification part of it, so we can see what your "code" looks like. Thanks!

Hi @Ben Harris - You'll probably end up needing to send a Web request to Bitbucket's REST API. Here's a good explainer on that: * How to make a web request from Jira automation to bitbucket pipeline? This is the endpoint to: Merge a pull request I highly recommend that you add a comment indicating that the merge was done…

BTW, I'm sure you already know this, but for anyone coming afterwards, here's some reference docs to help you "decode" the aforementioned smart values. * Jira smart values - text fields * Jira smart values - date and time 

Hi @Jason M_ - I'm curious what the point of "?<=" is at the beginning of your regex. My usual regex tester did not recognize it. But as to the replacement, I think the problems is that you actually need a lot less braces: {{issue.summary.replaceAll("(Put server in Maintenance mode for .* at )\d{2}:\d{2}:\d{2}",…

So glad it worked for you! For future reference, here's the documentation on Smart values in Jira automation. BTW, I'd appreciate if you could hit that "Accept answer" button up top. Thanks!

Hi @Aaron Rose -- You'll need to use a tiny bit of HTML with smart values, so like: The Target End Date has passed for the following issue: <a href="{{issue.url}}">{{issue.key}}</a>

Ahhhh, ok that makes a lot more sense. Yeah, let me know how it goes.

Whoops, reread your original post - you'd want to change the trigger to when it transitions to "In Progress".

Hi @Bryan Harmon (Lost Boys) - Wouldn't editing the top-level task's latest comment possibly be a problem if somebody had come along and made a comment on that task? I would just add the list of patches as a new comment. I believe your rule could be much simpler if you do something like this: I basically copied the work…

Hi @Andrian F - Rereading my original answers I think the final verdict is that this is not possible, as Automation does not have sort or diff functions, nor is it possible to reference to another smart value while iterating through a List. 

I found the questions. They can be found in an undocumented endpoint: https://YOURSITE.atlassian.net/gateway/api/proforma/cloudid/YOURCLOUDID/api/3/issue/{{issue.id}}/form/FORMNUMBER So, YOURSITE you know. You can find YOURCLOUDID by looking at the URL for your Atlassian Admin…

Hi @Babak Hosseini - where did you hear about {{issue.Previous status}}? I have not seen that in the Smart Values documentation and do not believe it is valid. Instead, this is what they list for finding the previous status: {{#changelog.status}}{{fromString}}{{/}}I tested this and confirmed I could see the status prior to…

Apparently forms data is stored in issue properties, so the data should be accessible that way. Here's a good Q&A about the topic: * How to access the form data in Jira Automations As @Simon Herd recommended, you probably definitely want to install Entity Property Tool for Jira (temporarily, because I believe it still has…

Maybe equals doesn't recognize booleans? Cause I think it might work without having to explicitly evaluate for true? {{#if(or(issue.Target End, NULL), issue.sprint.endDate.isAfter(issue.Target End.toDate))}}YUP{{/}}

Hi @Martin Härri - So, Jira implements "buttons" as transitions, that are part of a workflow, like @Anthony Morais laid out. These transitions can include validators that check that the Assignee field is not empty. Normally these transitions are used to move an issue from one step to the next (Open -> In Progress -> Review…

Hi @ingvarr - you mention that you "sort on concatenated date and id". How are you sorting?

Hi Kate - I would try this to see if it gives you what you're expecting: {{now.convertToTimeZone("Pacific/Auckland").withHour(17).withMinute(0).withSecond(0)}}

Why oh why doesn't Automation have an ELSE operator? I ended up having to have back-to-back IFs to get this to work:…

Caveat, it's 7:54PM in my time zone, so things might get a little trickier if say, at 5:01PM, you wanted the date to be the next business day at 5PM. You could probably do some conditional logic and use the isAfter function. Maybe in conjunction with toDateTimeAtStartOfDay.