Bill Sheboy Expert

Hi @George Tsemberlis Without seeing the specifics of your rule for context... There are several ways to do this using date / time functions: * Parse the date and time values as text, merge them, and then convert with the toDate() function and the specific format. I would try this way first. * Parse the time value into…

Hi @erica_bogosian I believe there are several ways to do this using a single Smart Values Condition...such as: * a conditional expression that contains both cases, combined with the OR() function, or * a single match() function testing both cases with a regular expression Here are some references for those functions: *…

Thanks for that information, @Olesia Zhukova Let's confirm one of those and check another hypothesis. Before we do that, would you please post an image of your complete rule in one single image and the complete audit log details for the execution? Those will provide better context to confirm we are all considering the same…

Hi @Harshvardhan Vala -- Welcome to the Atlassian Community! This was not a permissions or project settings problem, but instead the wrong smart value was used. Most rule actions with users need the accountId attribute, not the displayName one, to select a user. Thus, you could have used one of these expressions:…

Hi @Birthe Schmidt There could be several causes for what you see. Here are some diagnostic things to try... #1) How do you know the variables are parsing correctly? I recommend adding the {{#debug}} ... {{/}} function around the smart value expressions in the Create Variable actions, and then you may confirm the values in…

Hi @Claudio Rouillon Without seeing your actual rule and audit log details... Rather than using the list first function, I recommend using list filtering on the sprint's state to confirm it is indeed the active one. The reason is the lookup results are a list, and so is the sprint field, resulting in a list-of-lists. Thus…

Hi @Narendra Karapakula -- Welcome to the Atlassian Community! Without seeing the specifics of your rule and audit log details... The automation branch-related smart values are only available when using the related triggers (or specific actions). Please look here to learn…

Hi @Cecilia Rodriguez -- Welcome to the Atlassian Community! How are you cloning the work item / ticket? When doing that with an automation rule, you could use the Copy Forms action to attach the forms. Kind regards, Bill

Hi @Olesia Zhukova -- Welcome to the Atlassian Community! Adding to the suggestions from others... There are several additional possibilities for that rule symptom. Unfortunately, the messages in the audit log do not always match the root cause. Please check the following: #1) Who is the rule actor in the details at the…

Hi @Susan Cain Adding to the suggestions from @Izabela França ... I note a few things with your rule that need adjustment. But first: What problem are you trying to solve? That is, "why do this?" Knowing that will help the community provide better suggestions. What you seem to be trying is: GIVEN a future sprint exists…

Hi @Trudy P Claspill For your second limitation point, did you actually mean this? You can Jira customers (e.g., site admins) cannot manage group or role membership for the Automation for Jira user. If you have found a way to change the access of that built-in user, how is that done? Thanks! Kind regards, Bill

Hi @Gary Lazaro You may add the ROUND() function around your iteration and inside of the math expression. For example, this rounds to 2 digits. Please note I moved the division by 3600 inside the math expression before the rounding. {{#=}}ROUND( ( ( {{#lookupIssues}}{{timetracking.originalEstimateSeconds | 0}}{{^last}} +…

Hi @Renate Chalcraft -- Welcome to the Atlassian Community! Adding to the suggestions from @Walter Buggenhout ... I recommend not using any AI / bot-generated rule suggestions, even the built-in one from Atlassian. Such tools do not have access to your site's specific configuration and thus the generic guesses are…

Thank you for the additional information, @Vasu Dev This does sound like a one-time need, and as bulk-edit has been disabled in your organization (likely for non-admins) you could ask your Jira Site Admin to perform the update.

Hi @Vasu Dev First thing: what problem are you trying to solve? That is, "why do this?" Knowing this will help the community offer better suggestions, or perhaps other alternatives, because you seem to be describing this: GIVEN several Story work items AND each Story has Subtasks WHEN a rule is manually triggered THEN…

Hi @Falk F. -- Welcome to the Atlassian Community! The "Advanced Issue Search" is now renamed to "Search work items" in Jira Cloud. This was one of the many changes to the UX over the last year or two. You may find the feature from... * when viewing your project * on the left-side navigation, select Filters * and then…

Okay, I am out of ideas on this one, although I may be thinking of it incorrectly...I believe that property you set is on the workflow, not on the work item. That is why you cannot see it with the REST API endpoint I suggested. As next steps you could... * Wait for another community member to make suggestions * Work with…

That is curious...and, I have noticed intermittent problems over the years with creating questions detected as too similar to a prior one, particularly when the community app is having upgrades, performance issues, or an outage. I recommend you send an email to the Community Managers to take a look if something is up with…

Thanks for testing that, @Thomas Maenner Three more things to try (as I have not experimented with that specific property): #1) Let's confirm what is actually stored for a work item with that property. Using a browser tab, call the REST API endpoint for an example work item with the property currently blocking edits. The…

Hi @Thomas Maenner -- Welcome to the Atlassian Community! The entity property key is plain text for that action, but you are trying to pass a smart value. Please try removing the double-curly brackets around the key. Kind regards, Bill

As we already described, that field does not exist in the Lookup Issues result. Please see the other sources I provided for how to gather the information using the REST API endpoint for an issue search instead.

Hi @Boris Ahrendt -- Welcome to the Atlassian Community! First thing, for automation questions it is helpful to provide all of the context, with images of your complete rule and the audit log details...rather than just part of the rule. For the moment, I am hypothesizing the rule trigger is not relevant for the symptom you…

Hi @Mahnoor Arshad Yes, and...to the note from @Trudy P Claspill The Lookup Issues action for Jira Data Center does not support custom fields yet, and here is the suggestion to add those: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 For your scenario, you will need to use the REST API to gather the work items and…

Awesome! If this ends up solving it, please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @Andre Duarte -- Welcome to the Atlassian Community! There is a Multiple work item events trigger that would allow selecting multiple things, such as both create and update. When using that one, I recommend two things to reduce risks / improve troubleshooting: #1) The create work item event with rules has a racetrack…

You appear to be on a paid license level, and so your Jira Site Admin can submit a ticket to Atlassian Support at the link below. Users who are not at that admin level, or higher, cannot submit a ticket. https://support.atlassian.com/contact/#/

Hi @Laura Campbell Automation rules run after an event has happened. And so they could not detect someone is in the process of creating a page. Please also note the new Live Doc Started trigger fires when it is actually created...and so it is also after the event happened. Kind regards, Bill

Hi @Gary Lazaro I recommend not trying to manually parse the "pretty print" version of the time tracking values, and instead use the built-in seconds values, dividing when needed to get other units: {{issue.timetracking.originalEstimateSeconds}} {{issue.timetracking.remainingEstimateSeconds}}…

Greetings! Might the naming of this relaunched group confuse it with the Teamwork Lab group: https://community.atlassian.com/forums/Teamwork-Lab/gh-p/Teamwork-Lab As this one appears to focus on Atlassian tools, perhaps the word "tool" should be in the group name. Kind regards, Bill

Greetings, community! Who else is seeing an increase in items missing from the notifications feed (under the bell at the top-right of the page)? My best guess for the symptom is when multiple items are close together in time, or the same event for the same post (e.g., two people like a post), only one of them seems to…