Bill Sheboy Expert

Hi @Jeremy Derbord -- Welcome to the Atlassian Community! Yes, and...to Mark's answer: Some fields like issue type have several attributes. If you wanted the human-readable name for the issue type in your lookup, please use this: {{issuetype.name}} To learn more about the smart values and their attributes, please see this…

Hi @Roeland Schoppers I just tested and was able to update the default Roadmap field with a rule. Have you checked your JPD project, and Jira site, to determine if there are multiple fields named Roadmap? If so, you may need to rename the other one, or use an advanced edit with JSON using the correct custom field id to set…

Hi @Anthony Pugliese First thing, I believe the Parent Link field has been deprecated as Atlassian standardized the relationships between issues to use the Parent field. Next, your question seems to indicate you are using the Free license of Jira. If that is correct, I believe you will not be able to add additional levels…

Awesome; I am glad to learn that helped! Now a recommended next step: please explain this rule to another team member, ensuring you both understand how it works. That will improve rule knowledge and readiness for maintaining the rule.

Thank you for confirming your scenario. Please see the two approaches I described, and discuss with your Jira Site Admin to decide which to use: * single rule at the global scope, possibly selecting the specific projects * two rules, in different projects, and one can trigger the other

The syntax of the if() expression you are trying is this: {{if(someBooleanExpression, valueToReturnForTrue, valueToReturnForFalse)}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#if But you appear to be passing a number for the Boolean expression. If changing that does not help,…

With automation rules, timing is important. The better accuracy value will be {{issue.created}} as delays in automation rule processing could add significant time, particularly if there is an Atlassian outage and the rules need to "catch up". I am unclear on what you mean by "when you do the subtraction it will always be…

You may find some of the average information at the top of the chart, and the specifics for items by selecting them on the chart. One limitation of this chart is when multiple items have the same total time, they are grouped in a larger "cluster", which hides the individual details. Regarding filtering by status and other…

That is curious... Have you tried any tests with multiple items in both records and changedValues to confirm the correct item is returned with only one get() call at the end? In my experience, other automation rule, smart values which return lists AND have returned only one item seem to alias (or collapse data structures)…

Hi @Caleb Park I suggest using this article to help determine the smart value and custom field id for your field in rules: https://confluence.atlassian.com/automation/find-the-smart-value-for-a-field-993924665.html Kind regards, Bill

Hi @Lucy Olson -- Welcome to the Atlassian Community! Reviewing the information for the Sprint Report and the Velocity Report... https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-sprint-report/ https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-velocity-chart/ You…

Hi @Dominic Mercorelli 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 the community to offer…

Thanks, Dan! That's great! I did not know the modulo operator could be used in a stand-alone condition. Must be the math operation wrapper that allows that, and it certainly opens up possibilities for the other operators.

Looking at your rule image, the branch is to the issue just created: the epic. And then you try to link that to the most recently created issue: which is also the epic. So it tries to link to itself. As noted earlier, please try removing the branch, as that will then link the trigger issue to the most recently created one:…

Awesome; I am glad to learn that helped!

Hi @Nikola Perisic The reason that may not be working as expected is you probably want your 3rd rule to be triggered by the actions of the second one. That is disabled by default to prevent errors. When you want one rule's actions to trigger another, enable the "Allow Rule Trigger" option in the details of the downstream…

Hi @Fabio Salvi -- Welcome to the Atlassian Community! Based on your rule and audit log details, I suspect this is what is happening: * Your rule has project-level scope (but not in the "Mobile" project) * It creates the Story in "Mobile" project, and that works * Then the rule tries to branch to the Story in the "Mobile"…

Hi @Jan Michelle Lamboso -- Welcome to the Atlassian Community! There are rule usage limits and other service limits: https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ From what you describe, it is likely you are…

Hi @Thanasis Nikolaou -- Welcome to the Atlassian Community! Yes, and...agreeing with Nic's suggestions on disabling issue deletion, and... By the time the Issue Deleted trigger fires for a rule, the issue is gone and the links to the child issues are cleared. Although the rule has the deleted issue's key, that cannot help…

Hi @Csaba Vertessy When using the diff() function on two date (or date / time) smart values, you may use the prettyPrint unit of measure to make that human-readable. For example: {{issue.created.diff(now).prettyPrint}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference---…

Hi @Darren Nicas I am currently using the Free license of Jira Cloud, and so have no access to the audit logs to test my suggestions... That web response appears to contain an array, and not a list of values. This would explain why the get() function is not working as you expect. You could try grabbing the records and then…

Yes, that was the field I was asking about: {{issue.Contract.Invoice Expiry Days}} I have not worked with assets and rules, and so I wonder if because their lookups are dynamic that it is not evaluated in time for passing to the function. So continuing to use the variable will help: based on your audit log results it is…

Thanks, and that shows your rule can successfully add a hard-coded version to the existing ones. But you want to add the "Next unreleased version by release date". There are a couple of ways to do this: two updates or one update using data from the REST API functions. The second one is more difficult, so let's try the…

Well, I am out of suggestions. If your rule is matching what the log shows the dates are converting, but only sometimes. At this point I recommend working with your site admin to contact Atlassian Support: https://support.atlassian.com/contact/#/ After you hear back from them, please post what you learn to benefit the…

Hi @Mkrtich Tono If you invert the values (created before now) the values will be positive rather than negative. Or, you may add the absolute value function, abs, to the end of the expression. {{issue.created.diff(now).minutes}} or {{now.diff(issue.created).minutes.abs}} Kind regards, Bill

I just tried that with a company-managed project, using a single user-picker custom field and it worked. What type of project are you using: company-managed or team-managed?

Would you please post an image of your current rule and the audit log details? That will help to decide next steps. Thanks!

What is the source of that field? For example, is it a marketplace addon, and so may be a dynamically evaluated field? For fields like that, the must first be set to a created variable to capture the value...as they often will not work inside of functions. And then the variable may be used in the function, converting to a…

Thanks for that information! Regarding your responses, I see a problem: if an issue was in a sprint and does not finish, and is moved to a future sprint with no dates, there may not be a way to easily know that. You can try the field change smart values for added / deleted values, as my testing indicates they may be…

Yup, that is a good use case :^) How about a work-around...if you do not care about consistency of the first row being the same color? Try using the issue's id value instead, with inline math functions: {{#lookupIssues}}{{#if(equals(id,id.divide(2).floor.multiply(2)))}}issue {{key}} has an even id of {{id}}; {{/}}{{/}}…