Bill Sheboy Expert

I see four problems to fix in what you showed: #1) Your rule's definition of the variable varRelateIssues is incorrect. That may be seen in the audit log as there are no keys listed within the parentheses for the JQL. It should be this:…

For a question like this, context is important. So the community can help, please provide: * explain what is not working as you expected * an image of your complete automation rule in one image * an image of the rule action(s) where you are performing the calculation * an image of the audit log details showing the rule…

Hi @Viktoria Soldatova That should be possible using the date / time and math functions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ Perhaps start by using the startOfMonth() and endOfMonth() and…

Yes, and... In general I would not recommend renaming built-in fields. We do not know how the code accesses them in all locations (i.e., by name or by id), and so results may be unpredictable. When a differently named field is needed, creating a custom field may be better...accepting some built-in functions may not…

A variable is text and has no issues or objects, such as the attribute "key". When trying to send that email, please just try {{varRelatedIssues}} by itself. Please post an image of the audit log details showing the rule execution as that may help explain why the issues are not transitioning.

Hi @Kaminel -- Welcome to the Atlassian Community! For a question like this, please also post an image of the audit log details showing the rule execution. That may provide more context for this syptom. Until we see that... If you try the JQL for your first lookup to find tasks due next week, does it return any issues?…

Hi @Gal Fatal Removing those values from the Sprint field would invalidate the history showing the issues carried over between Sprints. Instead please consider discussing with the team what are the root causes for issues carrying over (e.g., challenges with backlog refinement, sprint planning, work focus, shifting…

Issues can be linked to ones other than "relates to". And so reviewing what I posted earlier, you will note that is the reason for the extra step with the created variable: to extract the specific linked issues with that link type only. Here is a complete rule with my earlier suggests. I recommend testing it fully and…

By default, automation rules do not trigger due to actions from other rules. This is to prevent errors / runaway looping. When you intentionally want the actions of one rule to trigger another, in the downstream rule, go to the rule details and enable the option "Allow rule trigger..." Then test thoroughly and monitor for…

No problem; glad to help! FYI...I am using Jira Cloud so please verify / test to confirm this works for your version of Jira. The technique below uses the math expressions and list filtering I noted earlier. Let's assume you want to update the percentage "Done" whenever the status of a child issue changes, and the…

Hi @Daniil Lazarev I am following up to learn if you solved this question yet. Thanks! Kind regards, Bill

Hi @Naven Kumar If the answer from Hans solved this, please consider marking the question as "answered". That will help others with similar needs find solutions faster in the future. Thanks! Kind regards, Bill

Hi @sharos.pillai I am following up to learn if you solved this one yet to extract the location information from the description field. If not, have you tried something like this yet to extract the location using text functions: {{issue.description.split("\n").match("Location of Workstation: (.*)")}} Kind regards, Bill

Hi @Doris Reinart I believe the round-robin assignment tracking is coupled to the publishing of a rule. And so when a rule is updated and republished, the rotation resets to the beginning of the user list. This is based on my observations and I see nothing in the documentation which describes this clearly. You could…

Hi @Shasheekant Patel I am following up to learn if you checked with the Atlassian Support team for this issue. Thanks, Bill

Hi @Gaurav Arora I am following up to check if you tried the method by calling the REST API endpoint to find the sprint needed. Thanks, Bill

Hi @Rita Arellano Short answer: That knowledge base article will not work for your field. Instead you may use the Send Web Request action to call the REST API with an issue search to sum the field. More information... Only a few fields are currently supported by the Lookup Issue action for that version. Here are the…

Hi @kauger That appears to be an Atlassian Marketplace addon feature and not a built-in feature of Jira Cloud. Perhaps check the marketplace pages to learn from the product's vendor if such tracking is possible: https://marketplace.atlassian.com/ Kind regards, Bill

Hi @Lloyd Randall No, that Summary page for JWM projects is not configurable for adding / removing widgets. Looking in the public backlog I did not find any suggestions related to this idea. You may want to scroll to the bottom of that page as it offers a link to provide feedback to Atlassian, and you could add more…

Hi @Logan Harvey -- Welcome to the Atlassian Community! Search filters in Jira using JQL (Jira Query Language) only find issues, and not other entities, such as users. (JQL is not a generic SQL.) You could find issues which are in-progress with assigned users, and use that information to create the reporting you describe,…

Does your scheduled trigger have any JQL to provide issues to the rule steps? That error message indicates your rule does not have an issue for a source of the edit.

Which user does the history indicate changed the Parent Link? I wonder...as Portfolio Epic is the top level in your hierarchy if Jira is already clearing the field because it does not apply. Perhaps there is some work in-progress for the defect for this symptom: https://jira.atlassian.com/browse/JSWSERVER-24811 The way to…

Thanks, and I fixed my post. I should have tested that one and not just typed it in :^)

Hi, and thanks for that information, @Diana C It does appear that endpoint returns the URLs for some of the related work information, but it only returns a title and category for release notes (i.e., no content). If you want to try pulling the other information into an automation rule, please see this how-to article for…

In that case, please check the documentation for the application, or contact their support team via the marketplace page for the app.

Hi @Hafeez Ul-Rahman -- Welcome to the Atlassian Community! Are you using a marketplace app for these measures? If so, perhaps check the documentation for the app: https://marketplace.atlassian.com/ If you are not using a marketplace app, what do you mean by "time in status app"? Kind regards, Bill

Hi @Mary Kable -- Welcome to the Atlassian Community! Perhaps you could modify your JQL to also check the lastViewed: https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Last-viewed For example: project = yourProject AND NOT lastViewed > startOfDay(-5) ORDER BY Key ASC Adding the lastViewed check to your…

Hi @Randy Simes First, the match() function could have problems with any embedded line breaks / newlines on the match. To address that you may use replace("\n", " ") before the match() call. Next, as you only want a count, the iteration over comments and math expression are not needed, as the match() will produce a list…

Hi @Aisha M For a question like this, please post an image of your complete automation rule and the audit log details showing the rule execution. Those will provide context to help explain this symptom. Thanks! Until we see those... For an example issue with this behavior, if you view the history do you see the issue type…

The JQL expression in the last step I described would be used with a Branch on JQL as you wanted to transition those issues to the Planned status. Is that what you still want?