Bill Sheboy Expert

Hi @Vijay Andela -- Welcome to the Atlassian Community! On your first question, Jira Query Language (JQL) is a tool to find issues. It is not a generic SQL and has no features of such languages. You may investigate marketplace addons if you are looking for additional features: https://marketplace.atlassian.com/ For your…

Hi @Jayanth -- Welcome to the Atlassian Community! I am assuming you mean a Jira Automation rule. Is that correct? If so...please post an image of your complete rule and of the audit log details. Those will provide context for the community to offer suggestions. Until we see those... There is no need to create a variable…

No, and the speed of removal depends on your project type: For a company-managed project, they will vanish from the backlog when marked as "Done"...which is why JQL (or viewing the issue directly) is needed to remove the sprint value. For a team-managed project, I believe you will need to refresh the backlog page in the…

You have some extra curly brackets in that expression to get the number: {{issue.summary.substring(7,8).asNumber.plus(1)}} To combine that with the other value, grab the left part first, followed by the number, and then followed by the right part:…

Hi @Kiley Bublitz -- Welcome to the Atlassian Community! The sprint scope includes what was in the sprint when it started, and so...one way to address this symptom is remove the completed items from the sprint before starting it. The key is finding them using JQL and then removing the future sprint from their Sprint field.…

Hi @Hakim Belkouch Without seeing your complete rule for context... Where is the number value you want to increment? It appears to be part of the Summary of the first issue (i.e., the Epic) to be cloned. In that case, you could use text functions, such as match(), to extract the value from the Summary, save it in a…

Hi @Philip Witt -- Welcome to the Atlassian Community! The structure of your complete rule will determine if this scenario is possible. To confirm this, please post an image of your complete rule in one single image for context. (This may be captured with an image capture tool or browser add-in for scrolling-page capture.)…

Hi @Khira Niemeier Please see my response to your other question, for the same need, here: https://community.atlassian.com/t5/Jira-questions/Re-Re-Smart-Values-Linked-Issues/qaq-p/2820601/comment-id/1053889#M1053889 Kind regards, Bill

Hi @Pramodh M For this scenario, I believe the rule needs to save the newly created Epic's key in a variable before the branch, and then that variable is used to set the parent field as each issue is created inside of the branch. Kind regards, Bill

Hi @Khira Niemeier The issuelinks smart value is a list of values, and so a list iterator must be used to access the values and filter them. And the structure depends upon the link direction: inward, outward, or both. Putting this ideas together... First, I recommend using this how-to article to better understand the…

In the advanced branch, it needs to split the values. Please see the original post for context. * advanced branch:* smart value: {{varLoopValues.split(",")}} * variable name: varLoopVariable Also as you create a rule, it can help to write values to the audit log to assess progress. I recommend adding the variable to the…

Hi @Ramsi Hawkins -- Welcome to the Atlassian Community! One interpretation of this behavior as "polluting downstream reporting" (as you describe) may be contrasted with another of "reporting the history of what happened". Clearing the Sprint field of prior values removes the history of the issue, preventing both teams…

You are missing the outer parentheses that @said kouzibry suggested. What is the type of this custom field? That may impact the syntax used for the JQL. Next, when there are multiple values in the trigger issue, are you trying to match on any values provided, on all values, or both possible cases?

If you want to link those issues to the trigger issue, use a branch on JQL rather than the Lookup Issues action.

Hi @Mat Levell First, I notice what appears to be a typo in the JQL for your Lookup Issues action: there is a space between the period and the custom field id. Next, you note the issues are in different projects. What is the scope of your rule: single-project, multiple-project, or global? A single-project scope rule can…

Hi @Aaron DeVore -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide…

Hi @Julia -- Welcome to the Atlassian Community! From what you describe, it is possible your different rules are colliding and updating the Epic repeatedly. For a scenario such as this, I recommend using one rule to update the Epic for the basic case. To do so, please try: * Define the behavior you want for the different…

Hi @Marta Trindade -- Welcome to the Atlassian Community! If you can calculate when the holidays will occur, you could try using an automation rule with a scheduled trigger to add the issues once per year. If you are unable to calculate the holidays, you could create a spreadsheet with the issue data and import them once…

Hi @pvyas -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for…

@Asheesh -- I responded on the other thread as you are missing several steps to use the rule technique I described. Kind regards, Bill

Hi @Asheesh The rule image you show is missing several steps to use the technique I described: https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935#M531 Please review that post to correctly create the variables before the attempt to use the advanced branch.…

Thanks for that reference, and...if you scroll down and note the "Submit an idea" section, it shows one must be a Creator. The alternative is to allow all Contributors the ability to add ideas or use a form. Here are the references Atlassian provides for using a JSM form to create the idea:…

Yes, and...have you confirmed you have the correct smart value for your custom field sprintsEstimation? You can do that using this how-to article: https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html

Hi @Nur Fatin -- Welcome to the Atlassian Community! For team-managed projects, the People field type still does not provide the email address to automation rules. Here is the open suggestion to add that: https://jira.atlassian.com/browse/AUTO-519 The two possible workarounds are noted above: * Ask your Jira Site Admin to…

Please try the Condition selection "None match specified JQL".

One or more of the child issues in your Epic has no Fix Versions assigned. If that was expected, the fix to handle the case is to change the JQL for the lookup to exclude them: "Epic Link" = {{issue.key}} AND fixVersion IS NOT EMPTY If it is possible none of the issues in the Epic have values, I recommend adding a…

Please post an image of your current, complete rule and an image of the audit log details. Those may reveal a problem with the results from the Lookup Issues action.

Your custom number field would substitute in the example I provided. And so the value of the varLoopValues variable would be: {{varLoopValues.rightPad(varLoopValues.length.plus(issue."UT-IssueCount"), "X").remove("NULL").replaceAll("X","X,").substringBeforeLast(",")}} Assuming that is the correct smart value for your…

Please clarify what you mean by remove / replace. The number field will work with the rightPad() technique to branch for a number of times: https://community.atlassian.com/t5/Automation-articles/Branching-over-smart-values-in-Jira-Automation/ba-p/1741935#M531

Hi @Lior Efraim Please review the math expression syntaxes, and then try this one: {{issue.startDate.plusDays(issue.sprintsEstimation.multiply(21))}} And, when using a smart value nested within another function, the extra curly brackets are usually not needed. Kind regards, Bill