Bill Sheboy Expert

Sorry for all of the updates; there is something "glitching" when I posted that one.

First for the error you see, there is an extra left-curly bracket in there. As a tip, I recommend writing stuff like this in an external editor which shows pairing for parentheses, brackets, etc. Next for the rounding: this cannot be done with the inline math, as that is using integer math because the week number is an…

Hi @rpatrick I do not believe it is possible to add a comment when creating a work item. It must be created first and then comments can be added. Where were you able to create one and add comments at the same time? Next, and assuming the comment is added later, you appear to be extracting zero-to-many email address values,…

Hi @Lisa Yeager In my opinion, it is both a good and a bad thing that Jira is so configurable (and continually improving)...leading not just to "feature / field sprawl" but also collision, confusion, etc. Sticking with the "good" from configuration... Perhaps start by understanding your value stream, and creating a visual…

Hi @Michelle S Short answer: that is not easily possible (or even a complete solution) with automation rules. First thing, every possible thing that can change in a work item is not recorded in the changelog provided to automation rules. The two reasons for this are: app errors, and marketplace apps / addons. * Some types…

Hi @Zaine Abaddin 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 * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a…

Hi @Céline - Maestrel Well done finding a workaround for your own question! FYI -- The reason the branch did not work for this scenario is branches which could be on more-than-one-thing are executed in parallel and asynchronously, with no guarantee when the branch will complete...up until the last step of the rule. This…

Hi @Zoe Rowley -- Welcome to the Atlassian Community! Creating the new Epics and updating the remaining ones from the prior quarter can be done using an automation rule. Please look here to learn more and get started: https://support.atlassian.com/cloud-automation/docs/jira-cloud-automation/ Regarding the use of financial…

Hi @Satish Dhamankar -- Welcome to the Atlassian Community! In my experience with this topic, I have used Jira and Confluence to track improvement initiatives, including value stream mapping for Kaizens, etc., although I find external partner, shared collaboration boards better than those provided by Atlassian. And while…

Thanks, @jira_admin_cu for confirming the scenario. Let's stay with the thread started by @Trudy P Claspill as she describes the changes to your rule as what you showed appears to be branching on the incorrect issue for the scenario.

Thanks for the images, @Louise Woods You appear to be using financial quarters, shifted where: Oct - Dec 2025 is in Q1 of 2026. Is that correct? If so, one way to solve this is to remove all the conditions, and instead increment the date by 3 months, then get the quarter with the format function. Assuming your Target End…

Thanks for that information, @jira_admin_cu It seems your scenario is this: GIVEN a Defect issue AND it has one-or-more linked issues blocking it WHEN one of the linked issues moves to Done AND all of the other linked issues are also Done THEN transition the Defect to "In Progress" Is that correct?

Hi @Louise Woods The resolution of your images is a bit low, making it difficult to see the specifics. And without seeing the audit log for the rule execution, I suspect there is a missed case / scenario and so the rule is always falling through the final else case. If you post the log and higher resolution images, that…

Greetings, community! For the present time, I recommend not using this new rule feature to add conditions to triggers. There are known racetrack timing problems with some triggers whereby the data may not be completely available when the rule starts; the work item can even be in an unstable state with no work item type…

Hi @Dd For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution * explain what is…

Hi @HaRsHaS' V Would you please clarify your question? For example, do you want to do one of these: * when a Resolved work item has its Resolution field cleared, then do ??? * when a completed / done work item is transitioned backwards from completed / done Status, then do ??? * or something else And, what do you want the…

Hi @jira_admin_cu What is the relationship between the Defect Issue you want to update and the trigger issue for the rule? Knowing that will help clarify how to structure your rule. As written, this is what your rule is doing: GIVEN any trigger issue linked to other issues as "is blocked by" WHEN the trigger issue…

Rather than using the Link Work Items action, you may use the Edit Work Item action with an advanced edit with JSON: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Linking-issues

You could use the substringAfter() function to remove the first occurrence of "years-" from the value: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#substringAfter--String-separator- Also, please confirm you have the correct delimiter as your example shows comma-space but your split()…

Hi @rachel rutti Yes, this is possible, and... When the Story is created (and triggers the rule) there are two ways to access that information in the parent Epic. * Use an if / else condition block and the Related Issues Condition to check the fields of the Epic with JQL, and then perform the updates to the Story * Load…

Hi markus.neuwald@canon.at Short answer: you could try using the REST API endpoints, called with the Send Web Request action, to do this. For the scenario you describe of updating / replacing the Description field from another work item, one could use the Lookup Work Items action with JQL to load it, and then reference it…

Hi markus.neuwald@canon.at It is not possible to configure the breadcrumb display levels. Here is an open suggestion related to what you note to show the Epic link when viewing a Subtask: https://jira.atlassian.com/browse/JRACLOUD-76578 Kind regards, Bill

Hi @Sam Campbell -- Welcome to the Atlassian Community! Short answer: I do not believe that is possible with built-in features. There are no changelog-related operators for CQL: https://developer.atlassian.com/cloud/confluence/advanced-searching-using-cql/#field-reference And, I do not believe there are any publicly…

Thanks for that information, @Kelsi Flores This sounds like a problem with the type of link added. To provide context to solve this, please post images of: * your complete rule in a single image for continuity * an image of the action where the link is added * an image of the audit log details showing the rule execution,…

Hi @ManuA Please see my post regarding the differences between the format "YYYY" and "yyyy". It is likely many customers use calendar-based years rather than week-based ones. And, for @Hermance NDounga -- I respectfully suggest not accepting a solution on behalf of the people asking questions when they have recently asked…

Hi @Nicole Saenger -- Welcome to the Atlassian Community! Are you trying to set date fields in the JPD Idea? If so, that has a different format with a JSON expression represented as text, as compared to other Jira date or date / time fields. For example, to set a JPD date field to the current date, please use this: {…

Hi @Mark Short answer: I do not believe that is possible with built-in features of automation rules. Some parts of what you describe are possible, although you may want to investigate marketplace addons / apps for a more complete solution, or a custom-built one using the REST API endpoints. Regarding what is possible with…

Hi @Danielle Alota -- Welcome to the Atlassian Community! I recall this is a known problem with the Folder Created trigger and available smart values, but there does not seem to be an open defect / suggestion for it in the public backlog. A workaround I have used is passing the {{folder.id}} to call the REST API endpoint…

Thanks for posting your updated / working rule, @Thermal Developer Some comments on the things you noted: * Using the create rather than clone action may have resolved this if there was a "glitch" in the action due to repeated edits corrupting the stored rule data. That happens sometimes with rules, and can be tested by…

Ah, the JSON is incorrect for setting a date type field. Please try this one, @Louise Woods { "fields": { "customfield_10023" : "{{latestSprintEnd.toDate.jiraDate}}" } } You could also set the jiraDate format in the variable creation, eliminating the need to convert back to a date later in the JSON.