Bill Sheboy Expert

Yes, that could work if the issue key is in the summary. If instead the quarter / year is in the Summary, you could use the date/ time functions to dynamically build the expression for which to search in the Summary: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ Please note well:…

Hi @Maria Barac -- Welcome to the Atlassian Community! It is unclear when / if calculated JPD fields may be used in other calculations, so let's focus on your attempts with an automation rule... First, your trigger on Issue Updated seems to broad, and I recommend changing that to specifically check the fields using the…

Hi @Eyal Taylor -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions /…

Hi @kempili bhargavi -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have a rule that is not working as expected, please post images of the rule and the audit log details, and explain what is not working. Those will provide context for the community to offer suggestions. If…

Hi @Rafael Freymueller You seem to have solved the first part of your question. For the second part, consider using a Scheduled Trigger with JQL to return the issues which have not be updated in your desired timeframe (and which are in that status). Information on Scheduled…

Hi @Bilal When a sprint is created, there are no issues in it yet. Issues are added after the sprint creation. Your rule uses the Sprint Created trigger, and then tries to branch to issues in the sprint, thus it will not find any. To do what you asked, instead of using the issues in the sprint you may use the smart value…

Greetings community! To learn some of the challenges using pie charts in communication, rather than other visualizations or even a simple data table, please see information from Edward Tufte, such as in The Visual Display of Quantitative Information. Kind regards, Bill

Hi @Christophe Ventura -- Welcome to the Atlassian Community! By default, the actions of one rule do not trigger other rules. This is to prevent errors and runaway recursive looping, which potentially would lead to all rules halting due to "throttling" conditions. When you intentionally want the actions of one rule to…

Hi @vince margaria -- Welcome to the Atlassian Community! The solution approach you tried with Lookup Issues will not work for Jira Data Center as the lookup results do not include all issue fields. Here is the suggestion to improve that: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 The workaround for that in your…

Awesome; I am glad to learn that helped! Regarding the number of rules and the field copying... For some, having fewer rules and including more fields is preferred...even it it makes it harder to check what happened (in the logs) and increases the risk of errors. For others, having a rule for each field (or groups of…

Hi @Antonio Koronios What type of project are you using: company-managed or team-managed? If you are using a team-managed project, when you moved the Epic to another project, you were likely prompted if you also wanted to move the child issues. What did you select to do: move them, or not? If you did not select to move…

Hi @Bryan Fitzgerald By default, the actions of one rule do not trigger other rules. This is to prevent errors and runaway recursive looping, which potentially would lead to all rules halting due to "throttling" conditions. When you intentionally want the actions of one rule to trigger another, enable the following setting…

Hi @Pejman Farahi Testing a smart value for "empty" is completely dependent on the field type. The exists test will work for some field types and not for others because they are never empty: they just do not have a value for the UI to use. Please read all the other posts in this thread and others, and always experiment to…

Here is a how-to article for calling the Jira REST API endpoints using the Send Web Request action: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

To access issues in multiple projects, the rule scope (in the details at the top) is set to multiple-project or global. Technically speaking, once a rule has a larger scope, it is managed from the global automation area. Your Jira Site Admin can help with that change. Many JPD fields can be set with an automation rule,…

You should not need to use advanced edit with JSON. Instead, you may try typing / copy-and-pasting that expression directly in the field for the Edit Issues action. When the expression appears below the field, select it for use in the edit. Re-reading your original question: do you want to "set" the year or "increment" it…

Hi @Jacquelyn Mosby -- Welcome to the Atlassian Community! Please try using either of these functions: plusYears() function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-plus-unit--- withYear()…

Hi, @Tanguy Crusson Thanks for this information and the team's continuing improvements! For the "in flight" items which may / could require customer actions, what considerations have been made to add release target timeframes to the roadmap? For example, if the remaining, unsupported global field types are added for JPD…

Hi @Abdul Wahab Which report are you trying to use? What are you seeing when you try to use the report? There are only a limited number of reports for team-managed projects: https://confluence.atlassian.com/jirakb/view-the-sprint-report-for-team-managed-projects-in-jira-cloud-1442158544.html Kind regards, Bill

@Ismael please see my post above ^^^^ To update the parent issue with the sum of a custom field, you would need to gather the issues using the REST API, called from the Send Web Request action. Here is a how-to article for calling the REST API from a…

To help provide context for this symptom, please post images of: * the current, complete rule, in one single image * the rule details at the top, showing the scope, actor, etc. * the edit issue action * the audit log details showing the rule execution Thanks!

Hi @Danielle David I do not believe there is an out-of-the-box way to search for gadget usage in dashboards in Jira Cloud. One could call the REST API endpoint to gather the list of dashboards, and then iteratively call another one to get the gadgets for each one, finally searching for the gadgets to be deprecated. A…

Is this a one-time fix or a re-occurring one? * one-time fix* I recommend reviewing the issue change log / history and updating the field manually * re-occurring fix* First thing, review the other automation rules to prevent them from clearing the field * As I noted earlier, when the field was cleared is important, as the…

Thank you for the additional information, Sue! Assuming your rule is defined in the Software Project to update the Idea in the JPD one, you could: * use a JQL branch to access the Idea in the JPD project * then use Lookup Issues with JQL to access the correct "parent" issue needed from the delivery tickets linked to the…

Thanks for that information, Rita. I recommend not subtracting for this scenario, and instead adjust your JQL to exclude the Canceled issues and recalculate the sum / t-shirt sizing for the remaining issues. This will lower the rule complexity and risk of errors.

Hi @Daniela Cancino -- Welcome to the Atlassian Community! That is not possible with the built-in features of JQL. Some workarounds depend upon how often you want to perform this type of query and your cost / effort constraints: * need this one time* manually review the built-in sprint reports and record the sums * export…

Hi @Pramod.Kumar.Ojha For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * when using Cloud, what type of project is this (e.g., company-managed, team-managed, etc.) * an image of your complete automation…

Hi @Jayanth Assuming you mean the total time spent in a specific Status... Short answer: That is not easily possible with automation rules. Without a marketplace app, there are at least four approaches to gather time spent in a specific Status: * use the built-in, Atlassian interpretation of a Control Chart report * use an…

Hi @Rita Arellano Your rule is updating the Size Estimate for the Epics, and so you could create a JQL statement to find Epics where the field is empty. With that JQL, you could use a Scheduled Trigger rule to find / update the Epics: * clone your current automation rule, and modify it to process the existing Epics* change…

I would not advise that approach; issue transition may involve lots of things related to workflow, and so using the specific Transition Issue action is safer, like this: * ... * action: edit issue, with your JSON variable * action: re-fetch issue * action: transition issue