Bill Sheboy Expert

Thanks for that information. Once an issue is completed for the sprint (i.e., moved to the last column of the board), it is done...and so I would not expect it to appear in a future sprint.

Hi @Jeff Hooper Two issues with your rule... First, you are trying to use an "Issue matches JQL" to test a created variable. That will not work as the variable is not part of an issue. Please try an advanced compare condition instead. Next, branches have some behaviors to understand as they impact your scenario: * Branches…

Sorry for my long answer; perhaps I gave too much information... I strongly suggest considering: why do you want that field in sync for the issues in the entire hierarchy? Although the rules can do this, it may not be a better answer to the problem you are trying to solve. For #8...when an issue such as an Epic is deleted,…

Hi @Joanna Nejfeld What do you mean by "backlog preview"? Do you mean the backlog view for the current sprint, a future sprint, or something else? Please post an image showing the view you mean, and which does not show the issue you are describing. That may provide more context for the community to help. Thanks! Kind…

From the information you provided, I infer you have the Premium license level of Jira Cloud: * Otherwise the function portfolioChildIssuesOf() would not work * And, running a global automation rule on this scale may only be practical for a Premium license; otherwise the site would use up its automation limit for global…

Hi @Jacob Turley You cannot use a literal value (e.g., "momentum") as the starting value in the expression. Please try storing that literal in a created variable first, and then use that to create your new version name. Or...build the entire thing in the variable in one step for use later: * action: create variable* name:…

Hi @Jiten Khanna First thing, have you investigated why those child (and grandchild) issues' values for the field are different? Were these entry errors, planned differences, or has the issue hierarchy changed in a way to make them incorrect? Knowing this will help guide the scope of your change...because using an…

Hi @Juniper Emnett If you can write a JQL statement to find the "child" issues based on the field values, the answer is "yes". To do this, please try creating an automation for Jira rule, triggered on the conditions for your scenario. This means you would either need several rules for an "always accurate" Rollup Revenue,…

Thank you for clarifying the problem you are solving. Before you implement something in a rule to measure this, have you discussed with the team why the assignee and status values appear to be changing frequently? Often such symptoms are caused by process issues, and so a discussion may reduce / eliminate the need for the…

Please review the data/time formatting information here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#-- That describes the use of the format() function, including a reference to the supported DateTimeFormatter values. For example, the one for the complete day of week name is:…

I am glad to learn that worked for you. And I have not found training like that for automation rules. My recommendations to learn more would be: * periodically review the documentation to look for updates * watch / read community posts (questions, articles, etc.) to learn from others * create a test project to experiment…

Hi @Ben van den Berg What problem are you trying to solve by doing this? Knowing that may help the community to offer better solution approaches. For example, if your audience for these emails are Jira users who want to follow issue changes, couldn't they review the issue history directly or just watch the issues? If…

HI @Abhishek Kalamkar Adding onto the answers already provided...you note wanting to name your new, saved filter using the just-created version's description. What information are you putting into the version description? It is possible that your description contains text which cannot be saved as a filter name, so please…

Hi @Ste Wright This could also be done using the date/time formatting functions to capture the day of week for the date, without the need for the if/else. And when a select field was still desired for the day of week field, that could be converted from text to select field, id value with a Lookup Table. Kind regards, Bill

Thanks for that information, Michael. Is this seems information to support a short-term (and not permanent) investigation, perhaps consider using the advanced search to find all issues for a time range, export them to a spreadsheet, and then perform the analysis there.

Hi @Michael Bevilacqua That is not possible with the out-of-the-box JQL features. What problem are you trying to solve by doing this? Knowing that may help the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Anthony Roldan Other than a case of a one-time-usage rule, I am unclear how this would work long term. Wouldn't the "starting point" need to change over time? Regardless... A few ways to do what you ask are: created variables, an "anchor story", and entity properties: * With a created variable saving your start date as…

Hi @Caio.Queiroz -- Welcome to the Atlassian Community! I recall when I last tried this...the property information needed to be in quotation marks, so perhaps try this: {{issue.employee.properties."key"}} Where "key" is the name you provided for the property. Kind regards, Bill

That seems to exclude team-managed project, field problems. At this point, I recommend working with your Jira site admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/ They may see something in the logging for your site which we are missing. When you hear back from them, please post…

Hi @ANISH TANEJA Adding to Laurie's answer: Some of the issue fields are not shown in the drop-down lists for rule actions. Instead they must be accessed by their smart values, and updated with JSON for edits. And...smart values are name, spacing, and case-sensitive. To learn if a field is supported by rules, and what its…

Hi @Drew Nedderman First thing: what is the purpose of this board showing two projects? For example, often this technique is used to create a view which rolls up information from different projects...and such boards are treated as read-only: any changes needed to the source issues (projects A and B) are made in those…

Hi @dayselmg96 -- Welcome to the Atlassian Community! No, you cannot use the created time of an issue as an event trigger. Instead rules can use a Scheduled trigger, with JQL on the relevant issues' fields (such as created) to do what you ask. Please look here to learn about that trigger and JQL to get you started on…

Hmmm... Is this a team-managed or a company-managed project? You can see that information at the bottom of the left-expand area on the page. My next idea would be "I wonder if someone has either altered the permissions of the Automation for Jira user, or severely locked down permissions in your BA project." Neither of…

Oh...now I see what's happening: this is a branching and created variable effect. --------- First thing, there is only a "create variable" and no "update variable". More about why that is important in a minute. Branches on one-and-only-one thing (e.g., branch on parent, branch on current issue, etc.) essentially are run…

Hi @Renee Troiani Following this thread, I did not see this information yet so I wondered... 1) What is the scope of this rule: is it global or for one project? 2) Have you tried adding the project (i.e., BA) to that JQL statement to observe the impact? For example: project = BA AND status != DONE AND summary ~ donation…

Thanks for that information, Daniela. What exactly did the Atlassian Support team indicate was not accurate in the documentation for those two rule actions?

Hi @Finch Grace What are the plans to add a disable option for this feature before this is added for company-managed projects? Ideally, a disable at a site-instance scope and not project-by-project scope, to reduce the work for Jira administrators. As others have described, this is quite a change to the UX and some clearly…

Hi @Niklas Borgstedt I wonder...rules which have been edited too many times can get "glitched" by the rule editor. (There is no explanation why other than something gets broken in the saved rule.) Let's try this: disable your existing rule, re-create your rule as a new one, and then re-test to observe the results. Kind…

As there is no comprehensive documentation for automation rules, experimentation is often needed to figure things out :^) I encourage you to create a test project in Jira, just for testing / playing around with automation rules. This can help to build and test complicated rules, and then copy them over to the desired…

I have seen that question asked before and I do not believe there is a way; that DevOps trigger runs for each impacted issue. One work-around is to check if the version is not yet released using an advanced compare condition, and only then proceed with the Release Version action.