Bill Sheboy Expert

My mistake: I recalled there was a hack that allowed creating the if/else and dragging it into a branch, but I just retested and that is not possible now. For the second approach, no: create the varPriority variable inside of the branch. You note that the priority can change by component. If we assume the epic has multiple…

Understood: they want to see all teams listed with data, not to add the story points across the teams. I suggest sketching out what this might look like, and what questions you want to answer with the overview. And then look at the marketplace to learn what might help.

Please try this to include just the summary and status name values for each of the inward and outward links. Just iterating on issueLinks will not work for this case. {{#issue.issueLinks.inwardIssue}}{{summary}}: {{status.name}}{{^last}}, {{/}}{{/}} {{#issue.issueLinks.outwardIssue}}{{summary}}: {{status.name}}{{^last}},…

Ah, and thanks. The missing part of the symptom was "when using multiple email address values in a custom field..." I am glad to learn the support team was able to help. As a precaution, I suggest updating your rule to add replaceAll(";",", ") so it can handle someone entering semicolons in the field.

That, I cannot answer. I suggest waiting for others in this community to respond, doing an internet search, and possibly checking in the developer community for similar questions: https://community.developer.atlassian.com/

Did you also add the lookup issues action, as I cannot see the remainder of your rule. That error seems to indicate that is not present yet. Please see my earlier responses for details. Thanks!

Thanks for the clarifying information. Automation rules trigger *after* the event, and so your rule will not run until after the issue is created.

Hi @Robert Di Falco You may also want to look for answers in the community group that is specifically for Jira Product Discovery: https://community.atlassian.com/t5/Jira-Product-Discovery/gh-p/jira-product-discovery Kind regards, Bill

First thing: well done figuring this one out! Okay, you are on track with the approach of creating a variable and using that to set the priority. Unfortunately, variables cannot be used in smart value, list filtering (which would make this easy.) Just to confirm your use case, which of these applies: (A) based on the…

Well, that should work. You appear to be the site admin for a paid Jira license, so I suggest submitting a ticket to Atlassian support here: https://support.atlassian.com/contact/#/ They may see something we are missing in their logging. And when you hear a response, please post back here what you learn to benefit the…

I am glad to learn that worked for you! The same technique works for Jira Cloud with Lookup Issues, and it is quite handy for reporting emails send by automation.

Hi @Kim Mirasol Where/when are you seeing that pop-up: when creating the rule, some other time, etc.? (I was unable to view your video to see your example.) And for a question like this on automation, I suggest posting images of your complete rule and of the audit log details showing the rule execution. That may provide…

Hi @Matias Peralta -- Welcome to the Atlassian Community! Adding to what Mark suggests... You note you are using a team-managed project. Those projects use the field "Story point estimate", and (at this time) automation rules can only set that field using the JSON edit. Would you please show a screen image of your complete…

Hi @john.fennell This is not possible with out-of-the-box JQL features. Assuming no scope changes, the following JQL shows what is in the active sprint: project = myProjectName and sprint IN openSprints() I believe there are marketplace addons for JQL which support such queries for sprint scope. And the built in reports…

Terry, is this rule/custom field in a team-managed or in a company-managed project? If it is for team-managed, there is an open issue where custom fields cannot be used in the TO address for an automation email: https://codebarrel.atlassian.net/browse/AUT-131

Hi @jelle van den broek -- Welcome to the Atlassian Community! To do this from outside of Jira, you could create an application calling the REST API with a JQL statement, such as: fixVersion IN (yourTargetVersion) Kind regards, Bill

Hi @Terry Reese -- Welcome to the Atlassian Community! That should work...what is the type of your field: text, user, etc.? And, if you write that custom field to the audit log, what do you see? One more thing to check...Smart values are name, spacing, and case-sensitive. To confirm you have the correct smart value, please…

First thing: your rule is missing a branch on "Most Recently Created Issue"...or you could change your smart values from: {{issue.summary}} to {{createdIssue.summary}} to reference the most recently created one. Branches allow you to loop processing over related issues or smart values. You can learn more about them…

Hi @Miloš Todorović Would you please post images of your complete rule and the audit log details, showing the execution of the rule? Those may provide some context for the symptom you are seeing. Thanks! My hypothesis: you are missing a branch to "most recently created issue" after the task create and before the email…

Two changes to make: remove the JQL from the scheduled trigger, and add a Lookup Issues action to use that JQL before your condition test. Scheduled triggers may be used with or without JQL to gather issues. For your use case, we want "no JQL" so the lookup can handle the issues.

I do not believe that is possible with the built-in email handlers. Any updates to the comments would be listed separately in the issue history. Perhaps there is a marketplace addon with improved email handling that can perform this in one step.

Hi @Steven Johnson Yes, that should be possible using the smart value, text functions to extract from {{issue.labels}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ Please note that there could be multiple labels, and so you may need to iterate over that list field to find what you…

Hi @Julia First, a disclaimer: I am using Jira Cloud and not Server / Data Center, so I cannot verify this suggestion. Your Jira version has bulk operations on {{issues}} for a branch or scheduled trigger, and I believe this will work, where you may change the priority names for your own:…

Hi @Jonathan Parsons Step one: make it work. Step two: make it "better". You are on a good track that a long, simple rule could solve this, and you could do that with an advanced branch over a list of teams (either from the epic or from a created variable), and then use conditions on the component to add either 4, 8, or 12…

Hi @Lauryn Butcher Some of the quotation marks in the JQL are the open/close marks (note the left/right slanting) rather than generic quotations. Please try replacing those. Kind regards, Bill

Please take a look at that second documentation link I sent; it shows two examples of how to do this, using the single-select id or the value.

Hi @Cesar Payamps That seems a bit more complicated, and I am having trouble visualizing what you mean. Perhaps if you add images of your rule and the audit log details, and describe what is not working, it will provide some context for the community to offer suggestions. Thanks! Kind regards, Bill

Hi @adam.quinn I have not done what you ask, and I expect it is possible with a global-scope automation rule, walking the issues until you find the target (Issue A) to link when Issue C is created. You appear to be on the Premium license, and so the execution limits for global rules are less of a factor...however if you…

Hi @Wilson Lai No, and there are a least a couple of work-arounds... A) Let's say you wanted to just do this with quick filters...You could use two quick filters such as: * Name: next release, with JQL of: fixVersion = earliestUnreleasedVersion() * Name: later releases, with JQL of: project = myProjectName AND fixVersion…

Hi @Emil Emilsson With 30 values, the possible built-in solutions are going to be a bit brittle. For example, if you try this with an automation rule you probably cannot do this with a long if/else set of components as rules have a maximum number of around 60 components, and each option would take 2 components: the…