Bill Sheboy Expert

@Simon Chan thanks for your detailed responses to the questions! I feel a "gap" is still the missing alerts when queued retries exist for more than a few minutes... Some customers seem to create cascading rule chains, primarily due to the absence of serial processing of branches and scheduled triggers, the limits on the…

The log clearly showed the rule triggering itself, and you describe there is another rule creating the initial issue that triggers this rule. So the big question is: how will this rule prevent itself from processing if you re-enable that "Allow rule trigger..." option? The only way to do that is: * After the issue created…

Please try to stay in one thread when responding. That will help others reading this question in the future know if there are multiple possible solutions. Thanks! Your rule has a condition such that it only updates the Epic when its Story Points are greater than or equal to 0...but they could be null also. That may be…

Hi @Erica Robinson Based on the audit log, the rule seems to be triggering itself. Please check if this option is enabled in the rule details at the top: Check to allow other rule actions to trigger this rule... That option is disabled by default to prevent rule errors / accidental looping. It should only be enabled when…

Hi @Blake Berk -- Welcome to the Atlassian Community! First thing, I would try using the JSON encoding text functions without replacing anything: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#jsonEncode-- If that does not help, try using the replace() function with plain text rather…

Hi @Mathew Lederman Without seeing your entire automation rule for context... I note that you are iterating over the {{inactivePages}} and the closing symbol is in the wrong place, and so apparently messing up the table. Please try moving the {{/}} after the end of the row and before the end of the table: <table>…

Hi @SB First thing, I am not an Atlassian or marketplace vendor employee. I'm just another customer using the products and participating in the community. With that out of the way... It seems you are making a statement of opinion, but posting this as a question. Did you have a question? And I agree: it can be frustrating…

Hi @Marissa Wetzer -- Welcome to the Atlassian Community! Yes, that is possible. The rule could be triggered on a change to the parent issue's date, branch over each sub-task, and then update the date by the amount of change in the trigger issue's date. Here is an article from @Trudy P Claspill which describes a similar…

Hi @Joakim Edstrand -- Welcome to the Atlassian Community! Without using a marketplace app, modifying a Confluence page's content is possible with an automation rule, although it takes some effort and an understanding of the page content implementation: * create the page, such as with your rule action * use the REST API to…

Hi @Owen Vachell -- Welcome to the Atlassian Community! Adding to the suggestions from @Walter Buggenhout ... You note this is for a Jira Product Discovery (JPD) project. What type of field is this and where was it added? * JPD only has its "date" type field (which is a JSON representation of a range of dates), and * JPD…

Hi @K Rahul What problem are you trying to solve? Knowing this will help the community offer better suggestions. Until we know that... Altering the Original Estimate will prevent the team from seeing the original forecasted value, reducing their ability to learn how to improve their sprint planning, estimation, and…

Hi @Jonny When trying to extract the distinct versions from a Lookup Issues result, please consider that the Lookup Issues result is a list of issues and the Fix Versions field is a list. Thus a list of lists will appear like this: [version A, version B], [version B], [], [version C]... Adding that directly will attempt to…

Hi @Luisa Cruz -- Welcome to the Atlassian Community! Short answer: unless you have a small number of projects with active sprints and those sprints have a small number of issues, what you ask is not possible. I recommend considering a root cause discussion with teams: why are they using other sprint naming conventions.…

Hi @Michael McCormick -- Welcome to the Atlassian Community! The Category field for Jira Work Management (JWM) projects works more like the Labels field, although new values can only be created from the List view. I do not believe it is possible to pre-define a list of values in such projects. Just guessing...perhaps this…

Then I would add those status exceptions to the lookup JQL: AND status NOT IN ("Expired", "Closed")

I was not noting the fields exist (or not) in the issue types used. But instead that the {{issue.issuelinks}} smart value does not load all of the associated data by default for a specific issue. If it did, one could imagine a situation were a single issue with linked ones could pull thousands of others, in an ever…

Hi @Pamela.Dodge -- Welcome to the Atlassian Community! From the question mark at the top-right of the Jira pages, you may select "Give feedback about Jira" and submit a suggestion. I just did a quick check in the public backlog and found no open suggestions for an "undo edit" feature for Jira Cloud. Kind regards, Bill

Hi @Dorothy Callahan You are correct the parent / child relationship is different than the linking type of "is child of" using "issue links". Instead the branch on linked issues with the correct type / direction is needed. Also, as this rule will impact issues in multiple projects (or perhaps even globally) the scope will…

Hi @Martin Kovalcik 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 in a single image for continuity, * images of any relevant actions / conditions /…

Hi @Tushar Khandelwal First thing: this is the Atlassian Community, not customer support. People read / respond to posts when they want to do so. If you have an urgent request I suggest you discuss it with your Jira Site Admin for support. Next, where are you trying to perform that sum: somewhere in Jira or in the…

Thanks for that information. As this is for a team-managed project, you cannot change the filter...which makes a rule like this simpler, although the Move Issue action is still needed to add to the board. * trigger: scheduled * action: create issue, for the new Task * branch: to most recently created issue* action: move…

Thanks for confirming the issue types, and... As the branch gets each "Feature", the Lookup Issues action would then find the child issues for it with this JQL: parent = {{issue.key}} Then the story points may be summed with this: {{lookupIssues.Story points.sum}} That will work if you have a company-managed project. If…

Hi @Bharat Kumar Bondalapati Once inside of the iterator {{#lookupIssues}} ... {{/}} do not use the issue prefix as the fields are relative to the lookup. If instead you are trying to filter the results, that is not possible as data from outside of the lookup is not visible inside the iterator. Instead try adding that…

Hi @Mike C_ -- Welcome to the Atlassian Community! First a disclaimer that I do not work with Confluence automation rules often, and so my suggestions are based on my general automation knowledge. With that out of the way... Your rule branch is over Tasks but the action is trying to access the page and that is not…

Hi @Stephanie Ho You have asked quite a few questions, many of which may require a higher-bandwidth channel to solve. My first recommendation would be to meet with your Jira Site Admin to outline these needs and learn what is possible and who could help implement them. Next, I will try to summarize some answers to your…

Hi @Glen Brannigan Have you started and automation rule and it is not working as expected? If so, 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 in a single image for…

Hi @Ellie Tyler -- Welcome to the Atlassian Community! First. your rule is trying to use the {{lookupIssues}} smart value but it has not first used the Lookup Issues action to gather the issues for the Feature as you loop through them:…

Hi @Olivier CANU -- Welcome to the Atlassian Community! Without knowing more details about your scenario, some general guidance would be: Pause to define the problem you are trying to solve. Ideally, explain that to another person to help confirm your understanding of it. Read about automation…

Are you using an if / else block for each condition, as @Trudy P Claspill shows in her response: https://community.atlassian.com/forums/Jira-questions/Re-Drop-down-field-automation-of-emails-based-on-drop-d/qaq-p/2967258/comment-id/1110642#M1110642 Or individual conditions? Clarifying this is one of the reasons I asked to…

Greetings, community! In my experience, some causes of "WIP churn" / "WIP debt" for a team's workflow are: * confusing Priority and Classes of Service while using... * Work In Process (WIP) limits without considering team capacity, Service Level Expectations (SLE) and Service Level Agreements (SLA); where the key words are…