Bill Sheboy Expert

Hi @[deleted] If I understand your question, you want to create the new issue (a story) and add sub-tasks to that one. If so, after you create the new story, add a branch on most recently created issue, and put your create sub-tasks inside of that branch. That will link them up correctly. Kind regards, Bill

Hi @Michael G_ There are at least a couple of ways to do this: * using JQL to find the subtasks you want (which have the trigger issue as parent), use the lookup issues action to gather and sum the values * using an mathematical expression, an iterator on the subtasks, and conditional logic on the issueType, sum the values…

Hi @Kyle Mitchell -- Welcome to the Atlassian Community! You may find several community posts and suggested improvements on this symptom, some of which you may watch / vote for…

Hi! Please take a look at the comments from Luis on restricting the behavior of the Balanced Workload option, and... Regarding your comment, Assign Issues does not "reassign" issues as you note. It will just assign them unconditionally based on the options selected. Next for your scenario: what would you expect this rule…

Thanks for that information, Nina. It does not appear you made the change that @Gokaraju gopi suggested for your condition, to compare {{issue.summary}} to the text Write content. Did you try that? If so, please post an image of that rule and the audit log details, and an example issue (e.g. one from your CMP project that…

Hi @Ryan Johnson D You seem to describe your team is using a time-box for spikes, rather than sizing them with story points. Thus the team "commitment" at sprint planning is potentially lower than your expected velocity. (Of note, some teams also use a fixed sizing for spikes in order to time-box them.) I do not know of…

Hi @Valeria.Mejia -- Welcome to the Atlassian Community! Please take a look at the Assign User action, with the Balanced Workload option to see if that would meet your needs: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Assign-issue Kind regards, Bill

Hi @Dwaipayan Dey -- Welcome to the Atlassian Community! There are a few things to check for your rule, as you have shown it... When you note the field "actual end" is that a custom field you added, or do you mean another field? Whatever your field is, please use this how-to article to learn if your field is supported by…

Hi @Nina Baars Would you please post images of your current, updated rule...including the details of what you now have in the advanced compare condition, and of an example issue that would trigger this rule when moved to Done. Those things may reveal why it is not matching as you expect. Thanks! Kind regards, Bill

Hi @Connor Skiro Did you call the REST API from the rule using a webrequest with https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/#api/2/version-updateVersion Or, did you just update the fields in the issue? At this time, I do not believe there is a built-in automation rule action to edit a version. There…

That link I provided shows the format() function, and a link out to the examples for the format strings. Here is one to return the full month name for the current date: {{now.format("MMMM")}}

That appears to be a permissions issue. Other customers have seen that symptom for linking to GitHub repos. I suggest to contact the Atlassian Support team for this one; they may be better able to see what is causing this.

Hi @AldoCauchiSavona I wonder...currently created variables are always text type, so perhaps the gt() does nothing on that value. Please try converting the variable with asNumber before performing the comparison inside of the condition: {{#if(daysDifference.asNumber.gt(0))}} >> Change the date to the new date. {{/}} If…

Hi @Nick Youngerman -- Welcome to the Atlassian Community! Without more details...I expect this can be done in a single statement without any if/else structures, using a mathematical expression wrapping conditional functions strung together repeatedly: *…

Hi @Eleandia -- Welcome to the Atlassian Community! Yes, and...to John's answer: As these are team-managed projects, their custom fields, status values, etc. are each distinct. So that means there could be "challenges" with rules spanning multiple projects. For example, errors in issue transition, updating fields show as…

Hi @Sander Voskuilen -- Welcome to the Atlassian Community! Your advanced compare is referencing a specific status value's workflow transition in changelog, but I do not believe that is possible yet. They have information at the field level only. And so those expressions may be evaluating null to null, and so always…

Hi @Boldizsár Vermes -- Welcome to the Atlassian Community! My understanding is that created variables are text, and contain no typing information or attribution which would allow accessing them like a JSON array. And your second example has a similar challenge: the min() function can only operate on a number or date, and…

Hi @Dana.Harel I am guessing your rule uses the scheduled trigger to create the new, monthly issue. If so, please take a look at the date time functions for smart values, and the documentation on the format() function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ With that, you may…

Hi @Antonio Domenech Picó -- Welcome to the Atlassian Community! Adding to Hamza's answer... Currently, one rule cannot call another rule. But one rule can create the conditions which trigger another rule...when you enable the option that Hamza has noted. Please note: if your first rule has branches on more than one issue,…

Hi @Gyllchrist AGO If I understand your question, you want to: * when a version is released * create a new issue, Task * and include in that new Task a list of all issues released with the version. Is that correct? If so, what problem are you trying to solve by doing this? The version report already contains that…

As you indicate this was working and has stopped, I recommend working with your site admin to submit a defect to Atlassian Support to take a look: https://support.atlassian.com/contact/#/

Hi @Danish Magrey Those sections dynamically generate the JSON to remove/add the labels. They are used inside of the list, iterator for walking the from/to labels in changelog. For more details: * Please see the advanced edit for JSON help on remove/add of labels, as that was used to make the template you note.…

I do not know how to do that with the built-in features as it would need to set the value before the issue is created...AND...reference an issue field from a parent which could theoretically change value during the time the create screen is shown.

Hi @Nitzan Matalon Would you please post images of your complete automation rule and the audit log details showing the rule execution? Those may provide context for your question. Thanks! Regarding automation rules and post functions, those happen after the event, such as Issue Created. Are you trying to create a default…

Hi @Erwin Traas -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? What do you want to remind the team of with this email? If there is something not happening when expected perhaps a team discussion could help address this. And, when teams use the Scrum framework, they have a daily…

Hi @Chethan Swamy Gowda -- Welcome to the Atlassian Community! I do not believe there are built-in features just to count issues meeting certain criteria. Depending upon your Jira version, you may be able to use roadmaps and dashboards to show the dependent issues in hierarchal form. To get the count only, you may need…

Hi @Lisa Kerns What have you tried thus far to solve this one? If you have a rule started, please post images of your rule and the audit log details. Those will provide context for the community to offer suggestions. If you have not started a rule yet, what would this trigger upon: should adding any comment to an epic copy…

To do this with an automation rule, first you need to add a custom field to capture the "Sprint Completed". If you have a team-managed project, the project admin can add the field. If instead you have a company-managed project, discuss adding the field with your Jira site admin. For the rule itself, this would do it: *…

Yes, and others agree. There is an open suggestion to add Confluence updates to the linkedIssue() function for JQL to support including/excluding such changes by the updated link type. This one is 9 years old, so hasn't moved much: https://jira.atlassian.com/browse/JRACLOUD-35699 A work-around would be to investigate…

Hi @Dąbrowski Damian Yes, and...to Dirk's answer: Working with your site admin, you could view the complete list of rules and find the ones "owned" by the deactivated user's account. Your admin can then change the owner for the rule(s). If you have a lot of rules, this can be a bit cumbersome as there is no search for…