Darryl Lee Community Champion

Hi @Danilo Simic - I'm a little confused about the scenario since you're using "Field A and Field B" and it doesn't really make sense to me what you're actually trying to track. A real world example using the actual fields you are trying to track may lead us to a solution that is simpler. But just to answer your questions,…

Annnnd, just before going to bed last night I had another idea since Atlassian lets you set default values for Smart Values. Could that be used for the "Other" value? Why yes, yes it can. So then: { "update": { "Cause": [ { "set": {"value":…

Oh duh, I guess if you really wanted the options to be capitalized, you could convert them BACK with the handy capitalize function. { "update": { "Cause": [ { "set": {"value":…

So yeah, for this, you'd just need to generate a pipe-delimited list of your options, and paste it in twice. (Still need an IF/NOT to check for "other".) The match operator is kind of handy since it returns what it finds.

Oh wow. After figuring out the fix for "Other", I realized and tested to confirm that this could be done without any IF statements at all, IF you are willing to have your custom field options be all lowercase: { "update": { "Cause": [ { "set": {"value":…

Ok, didn't need the AND, since I can do regex alternation using the pipe (|) character. But I did need the NOT operator because Automation's isEmpty function does not work very well, it seems. So I added this ugly line after the other IF statements:…

Hey guys, just a few notes: @Stefan Salzl - the hashmark (#) is not just for iterating over lists. It's also used for the conditional if statement, and the {{/}} is how you close the if block. You linked to this already (sorry), but Jira smart values - conditional logic describes this, and it in fact works outside of…

Got it! I named my custom field Cause (you don't have to use customfield_xxx, which makes rules easier to read). This worked for me: { "update": { "Cause": [ { "set": {"value": {{#if(issue.summary.toLowerCase.match(".*(crash).*").isNotEmpty)}}"Crash"{{/}}…

If you just want the running total of work logged, I would create and test a newer, simpler rule, following the example @Mark Segall gives here: https://community.atlassian.com/t5/Team-managed-projects-questions/I-want-to-sum-up-Time-logged-against-sub-tasks-and-update-it-in/qaq-p/2081560#M5576 It simply adds time to the…

Hey Baris - I'm a little confused because in your original request you said you were trying to get a Sum of hours worked for all child tickets of an Epic. But in various places in your rule (both your original and your edited version) you refer to remaining estimate. I would double-check all your smart values to ensure…

To provide expand a bit on what Joe wrote, you'll need to use Jira Expressions from a third-party add-on to set up a Workflow Validator based on probably User Role or Group: One example is here:…

Hi - could be you (or one of the groups you're in) doesn't have permission to Browse Users and Groups. https://confluence.atlassian.com/jirakb/unable-to-browse-for-users-and-groups-120521888.html

Man... if only this worked: {{issue.description.eval(replacement)}} OH. I know why I'm not getting an error though. Automation must be interpreting my variable name, as well as "eval" as me looking for some additional property for description that doesn't exist. 

Dangit Bill, ya led me down the same path again. I can grab all the @mentions account Ids and Display names thusly: https://boomaster.atlassian.net/rest/api/3/user/bulk?{{#issue.description.match("\[~accountid:(.+?)\]")}}accountId={{.}}{{^last}}&{{/}}{{/}} And I can use that to generate a very nice set of replacement()…

Oh neat idea about multiple results. This would be the call: https://boomaster.atlassian.net/rest/api/3/user/bulk?accountId=557058:xxxxxxxxxx&accountId=5ffcb54xxxxxxxxxxxxxxxxx But I still think the issue would be replacing the @mention macros in the description text with the display names. I don't think a single match()…

Augh. I'm so close. Advanced Branch to search for accountids: {{issue.description.match("\[~accountid:(.+?)\]")}} And then I can even replace the code for mention in a variable: {{body.replace(mentionId.concat("]"),webResponse.body.displayName).replace("[~accountid:","")}} BUT I'm running into the age-old problem of…

Heh yeah, I've gotten as far as extracting mention accountids and looking up the display names, but then I'm trying to generate an email body thusly and it's failing: {{issue.description.replace.("~accountId:".mentionId,webResponse.body.displayName)}} So I guess you're saying we'll need to do something like finding all the…

Yeah, it's kind of annoying that you can do the reverse (programmatically generate a mention from an Account ID), like so: [~accountid:{{Squad leader.accountId}}] https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/ But I actually do think Automation is capable of this, albeit it is UGLY. Here's how…

Hi. I would think you want to check whether SLA is breached in the JQL.

Hi @Pauline Hild - You can also do this by having a different rule that is triggered by the Subtask creation (with appropriate constraints, of course). The key is to check the Allow rule trigger box for your status-setting rule, as illustrated here: Credit to @Robin Flood for the image from this answer:…

Sorry for the late reply here, but I was looking for an answer to the same question, and have to point out @Dominic Lagger 's answer is unfortunately incorrect, as @Christy Draicchio was asking for alerts about "the use of keywords on new/edited confluence pages". The instructions and screenshots Dominic provided are,…

From my reading of @Jayme Burkhalter 's original post, he wants to @ mention ... a portfolio manager Who is not necessarily an Assignee, Creator, or Reporter, So yes, if there is a Portfolio Manager field, then this should work: [~accountid:{{issue."Portfolio Manager".accountId}}] But if they're actually trying to "hard…

BTW, to find your account ID or those of others: The easiest way I've found to find my accountId is to click on my icon on the sidebar and then on the "Profile" link. In the URL you can find your accountId after the last "/" : Per @miikhy here:…

I realize this is an old topic, but this is precisely what we would like to do as well. A few years back @Radoslaw Cichocki {Deviniti} made this video with Tomasz Onyszko from Predica that talks about doing this with on-prem Jira: https://www.youtube.com/watch?v=_2OZuIDJeNw Radoslaw - have you and your team (and maybe…

Hi @bharath.veeramalla - what do you mean by "check on the time"? Are you looking to generate reports? Or just be able to look at a chart? Something like the User Workload Report? * https://support.atlassian.com/jira-software-cloud/docs/generate-a-report/#Reporting-UserWorkloadReport- *…

After proudly showing my solution to a colleague he commented: I was just using filters + subscriptions. To which I replied... He's exactly right. That's way easier. And the emails look much nicer. Your filter would be something like: assignee = currentuser() and resolution is EMPTY…

Ohai Bill! So as I laid out in my answer to @vdhanorkar's standalone question over here, I actually branched on {{lookupIssues.assignee.distinct}} in the "For each" so that I could access {{thisassignee.accountId}} for the nested JQL lookup and also use {{thisassignee.emailAddress}} for the To: in the email.

Success! Full rule: And details on the new second Lookup: So there you have it. BTW, I corrected your original mail body @vdhanorkar because you had {{issue.summary}} when you just need {{summary}}.

Ah, think you solved this previously, @Bill Sheboy by adding another JQL query for each assignee. Clever. https://community.atlassian.com/t5/Jira-questions/Smart-Value-Filtering-Comparing-Two-Lists/qaq-p/1959275 For option #3, you could use lookup issues and advanced branching to then notify the people...or send yourself…

Oh man! I'm getting close! Got the list of assignees and can iterate through it with Advanced branching, accessing {{lookupIssues.assignee.distinct}} like so (this is the "For each" section that shows up in the full rule at the bottom: But the problem then is my "filter" can't access the thisassignee variable…