Bill Sheboy Expert

Hi @Anu Given what you describe, perhaps you do not need that specific condition on other stories: when the rule triggers and the branch gets to the epic, you know you want the epic in progress also. Instead should there be a condition so the epic is only transitioned to in progress if it is not already in progress? Kind…

Hi @Yen Phan -- Welcome to the Atlassian Community! I just did a rule test for an entire month of dates, and the behavior appears to be similar to the other business day function(s): * if the source date is a business day, it returns that same source date * if the source date is a weekend, it returns the prior Friday…

Hi @Mouna Hammoudi For a question like this, please post images of: * your complete automation rule, * the action details where you are accessing the smart values, and * of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Thanks! Kind regards, Bill

Let's confirm something...what version of Jira are you using: Cloud, Server, or Data/Center? And, do you have any marketplace addons for JQL installed? Next, as Dave described originally, this is the format to mention someone in a rule comment, where you insert the specific user's account id value. That can come from a…

For the second condition I noted, you want an advanced compare condition and not a JQL condition: * first value: {{#changelog.Epic link}}{{toString}}{{/}} * condition: equals * second value: leave this empty Although your testing surfaces another case to cover: when the epic changes for an issue, both the old and new epic…

Please note I did not type in quotation marks in that JQL...Instead when I typed the id autocomplete found the name, and then substituted the account id. And...this was a method to find the account id values; they still must be used in your rule to effect the mentions.

Hi, @Darryl Lee -- Most of the times I see a similar question related to stripping off some form of markup like HTML, the eventual answer is: call a REST API function which can do that for you, outside of the rule and Jira.

Hi @DavidBernardoSI1996 First thing, I am not using Assets and so my suggestion is based on what I understand about rules. With the disclaimer out of the way... Once you are inside of a rule iterator like {{#lookupObjects}} it can only see that information at that point, and lower. And so referencing {{lookupObjects.Name}}…

Hi @Raheem Soomro -- Welcome to the Atlassian Community! Adding to Trudy's answer... Yes, Jira allows team to do that. And, as the team will be splitting their capacity across multiple sprints, the forecasting and reporting that Jira provides may be less valuable to you. The team may have struggles with focus, and knowing…

Let's try changing that second condition to check if {{#changelog.Epic link}}{{toString}}{{/}} is empty. And, the JQL for that branch should be: key = {{#changelog.Epic link}}{{fromString}}{{/}} AND issueType = Epic

Thanks for that update, @Nanda Do you know why that branch type is listed for rules in Jira Software projects, even when JSM is not installed? Kind regards, Bill

Hi @Alexander Münchrath -- Welcome to the Atlassian Community! Adding to the answer from Hana... Automation rules run (i.e., trigger) after something has happened. And for your scenario the rule could not trigger until after the issue has already transitioned. That would not help ensure the field is completed first. Kind…

Hi @Mathew Lederman Please look here for all the spirited conversations on the changes to the packaging model for automation rules: https://community.atlassian.com/t5/Automation-articles/Introducing-our-new-packaging-model-for-Jira-Cloud-Automation/ba-p/2446099 Kind regards, Bill

Hi @Gema Ruiz If I understand your question, your scenario is: Given I have a Jira project with documentation, and that project has a custom field containing a list of other projects When I manually trigger an automation rule Then that rule will create several issues in the projects specified by the list of other projects…

Hi @Mihail Chatlabashev -- Welcome to the Atlassian Community! First thing, that appears to be an undocumented smart value regarding rules, but instead is referenced for Forge apps. Next, when I try that in a rule it does produce a fully described URL. Would you please post an image of your complete rule, including details…

Hi @Deepika Dandala By "capacity planning" do you mean assessing the impact of people's availability on what the team can deliver in the next sprint / iteration? If so... There is nothing in out-of-the-box Free or Standard license, Jira that can help with capacity planning. If you want something in the tool for that please…

An easy way to find these is using an issue search and JQL... * navigate to Filters > View All Issues * enter some JQL like this* assignee IN (theUserName * As soon as you start typing, Jira will suggest a user name for you to select * Jira will autocomplete, replacing the user name with their account id value * grab the…

There are some missing pieces from your rule for this scenario. I noted these when I first suggested using the changelog: * First detect the child issue was removed from the epic; the current trigger and advanced compare cover this * Add another condition to check if the current epic link is empty, meaning the issue was…

Hi @adithya I am assuming that all of the boards you are asking about are in one Jira project. If not, please update your question to reflect this. Jira boards display issues based on a saved filter. And so issues do not get "linked" to different boards: if they meet the criteria of the filter for a board they will…

Hi @Anu Adding on to Trudy's suggestions... It seems you are using epics for two purpose: organize a large work item and classify work types (i.e., Prod Support, Tech Debt, etc.) Have you considered using something else for the classification of work, such as the Component field? Kind regards, Bill

I wonder... If you map out the flow to confirm the states and your processing timeline, could you capture when draft occurred in the issue (e.g., in a custom field, label, or entity property), and then either modify this rule (or use and additional one) to handle this case.

Well done, and thanks for posting that in the open suggestion as well! That will benefit the community...and perhaps Atlassian will update the documentation to match what you found for the additional value in that field :^)

For the child issue removed case, the rule must use the generic "Issue Updated" alone. Only then will the changelog work as I noted for detecting the case. After that change you may add the advanced compare condition I suggested immediately after the trigger.

Thanks for that information, and... In your compare, I note that you have quotation marks around the smart value. Please remove those and test again. Otherwise the "second value" will not match as it does not have quotation marks around it.

Yes, and...if that does not work, the smart value for the field may be incorrect. Sometimes a field's display name on screens is different than the smart value. You can check that using this how-to article to identify your smart value, or use the custom field id as an…

Would you please post images of your complete rule, the details of the action where you are using that expression, and of the audit log details showing the rule execution? Those may provide some context for what is happening. Thanks! Until we see those...if you look at that error message it shows there is a missing right…

No worries, as we are all learning all the time :^) I was suggesting that the smart value is incorrect. The smart value is name of a field the rule uses to access the information. Every field has a displayed name (on the screen), a smart value, and a custom field id. And sometimes the displayed name and smart value are…

Hi @dharm dutt You do not indicate how you are trying to do this: in some script / program, in an automation for Jira rule, in a spreadsheet, etc. Perhaps use whatever concatenation functions exist in your environment to build the URL first and then us it for the REST API call. Kind regards, Bill

Hi @Dave Bunt -- Welcome to the Atlassian Community! I believe there is a suggestion to add a start date/time to the basic scheduler, but until that is added have you tried to add a CRON expression and select the specific months you want to run the rule? Kind regards, Bill

That result does show what we expected, although it is unclear why the lookup's get() does not work. When I tested this same scenario/rule structure in a JPD project it works. The rule could be glitched from too many edits, so two things to check for that: First, disable the rule. Re-enable it, and then retest. If it still…