Bill Sheboy Expert

Hi @Troy Edmonds First thing, for a question like this please also include an image of the audit log details showing the rule execution. That will provide context for which steps happened, and other indications. Until we see that... Next, your rule conditions seem to be testing for LGA values and then making an assignment…

Hi @Ron Rodrigo -- Welcome to the Atlassian Community! To suggest a new feature, please use this page or one of the feedback mechanisms built into Jira: https://jira.atlassian.com/secure/Dashboard.jspa In the meantime, I am curious: what problem are you trying to solve? Specifically, why measure different time-in-status…

Hi @Marc Schadee I am glad to learn you found the workaround, and... FYI, the distinct was working as expected: it just did not match your scenario because the sprint field can contain multiple values, and "distinct" was over the sets of values in this case. For example, if the issues had these sprint values: * issue A:…

Hi margaret.lee@dzsi -- Welcome to the Atlassian Community! When viewing the Bug, have you tried selecting the Parent field and using the X at the right side to remove the Epic linkage? Kind regards, Bill

Hi @Clement Rather than using the Issue Fields condition, you could try the Smart Value condition and test with a regular expression: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#--smart-values---condition For this method, you will need to confirm you have the correct smart value for your…

Hi @Bryan Urias In my opinion, that Atlassian-written article is not super helpful at solving this scenario...particularly because it has some hidden assumptions and is quite inefficient. Be that as it may... If we assume it works, there may be a problem with one of the rule actions or the processing. Please review: * each…

Hi @Tehmina Aslam For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @Jasdev Singh The min / max limits for board columns do not prevent moving issues on the board. Instead they are visual indicators and reminders for the team. If those limits prevented moving issues, I hypothesize there would be unintended consequences for a team: * people may not move items on the board when needed *…

Hi @Samuel Kolloch Is there an existing feature or method within Jira that allows us to track the duration an issue stays in a specific status? Although the time in a status for an issue can be seen on Atlassian's interpretation of a Control Chart, that time duration cannot be easily reported / viewed for a list of…

Hi @Erfan Alvand This seems to be a duplicate of your earlier question: https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Custom-formula-to-apply-based-on-history-of-a-field/qaq-p/2724776 Kind regards, Bill

Hi @Erfan Alvand Because your rule trigger is when the value changes, you may use the {{changelog}} smart value: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- With that, you could check if the original value was non-blank, indicating that the value changed rather than was set…

Hi @Pat Schilling First thing, I suggest not having different fields where the display names only vary in capitalization. This will confuse users and potentially some Jira internal processing. Next, what types of projects are you using: company-managed, team-managed, etc.? This is relevant because automation rules easily…

First thing, please stay with one thread when responding. That will help others looking at this question in the future know if there are multiple solution approaches. Thanks! Next, you are not showing your entire rule, and so the context of where, how, and on which issue is being edited is unclear. Please post an image of…

Immediately after your condition: If: Project is one of A or B (to enable 'No actions performed' if rule run but didn't meet conditions) You could add a smart value condition to check the destination issue's project for the link. The project key for that issue would be this: {{destinationIssue.project.key}}

Hi @Paloma Alvarez Kachoski -- Welcome to the Atlassian Community! I recommend starting with this overview to learn where and how to write rules in Jira: https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation Kind regards, Bill

The rule trigger you show has selected the bulk handling option, and so the smart value is the {{issues}} one used, and not {{issue}} and so I wonder if there is something different for that list of values (similar to the current Data Center limitations with Lookup Issues). Again, I am using Cloud not Data Center, and so…

I am glad to learn that worked, and... Yes, that is the expected behavior for setting the parent later. Please see my original response as there are several cases to consider. The Issue Created trigger will only handle the first one: 1. When a child issue is created, and has a parent with the field set, copy the field to…

Hi @Thiyagarajan Manickam -- Welcome to the Atlassian Community! I am unclear what you are asking... Do you mean you want spaces around the hyphen? If so, please try this: {{issue.duedate.format("qqq - yy")}} Kind regards, Bill

Hi @Jishnu Unni -- Welcome to the Atlassian Community! There are at least three built-in ways to do this with Jira Cloud: * create a dashboard showing the issues, and send a weekly email with a link to the dashboard * make a saved filter to return the issues, and allow others to subscribe to the filter for a weekly email *…

Hi @Yogesh Ranjitkar The short answer is: no, there is no easy / efficient way to do this in an automation rule. What problem are you trying to solve? That is, "why do this?" Knowing that may help the community to offer other solution approaches. Until we know that information, and back to your question... You do not…

Hi @forabi I do not believe that is possible yet: the Version Updated trigger for automation rules does not detect when there are changes to the version approvers. This is likely because there appear to be no REST API functions to access those fields yet. Here is the suggestion to add that specific…

Hi @Hunter1428 As a reminder, I am using Jira Cloud, and not Data Center version, so please test any suggestions to confirm they work. Just to confirm is this for a single issue as you are showing a prefix of {{issue... for the expressions? First, try writing just the field to the log and observe what you get: #1) just the…

Did the new issue TESHRIS-155 have a both a parent assigned and value in the parent's field at the time the rule triggered? Are the parent and child issues both in the same project: TESHRIS?

Hi @Bill Williams -- Welcome to the Atlassian Community! I am glad you found that typo to fix the problem. And also...will your trigger issue ever have multiple values in the Fix Version field? If so, that JQL will need adjustment to handle one-to-many values: fixVersion IN (…

Hi @Gilad Waldman For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @Cristóbal González As the purpose of your rule is to set the Start Date once, have you considered adding a condition that the rule only proceeds if the Start Date is empty? Doing that would also address the potential problem of accidentally moving something into "In Progress" too early, as the the Start Date field…

Hi @Sascha Wiltenburg Have you tried checking both the trigger issue and destination issue project values with a condition before the rule proceeds? Doing that before the branches should eliminate the possibility of other projects causing the rule to proceed. Kind regards, Bill

Hi @Priti Manapure -- Welcome to the Atlassian Community! Wouldn't the individuals doing the work log time as they perform the work? That would manage splitting the time for tracking, and handle situations where one person's tasks are larger than others for tracking. Kind regards, Bill

Hi @Rafael Freymueller Yes, and...to John's suggestions: Are you trying to only update the newly cloned issue or others cloned in the past? If you only want to update the new one, please change your branch type to Most Recently Created Issue. Kind regards, Bill

Given what you describe, I would expect that behavior for the branch: * your rule is triggered on issue created, and so starts soon after the Task is created... * but it runs so quickly the subtasks are not available yet when the branch is reached (as you are still adding them). At this point, I recommend working with your…