Bill Sheboy Expert

Hi When using long-format list iteration, only data from that scope (and lower) is visible. Thus, outside work item fields, variables, etc. cannot be used. Worse still, there is a long-standing defect where some functions within an iterator can only interact with the first item in the list, regardless of how many items are…

Hi @Mahanth Prudhvi P I recommend also posting this symptom in the community bug thread: https://community.atlassian.com/forums/Community-Announcements-articles/Forums-bug-report-thread/ba-p/3183735 Kind regards, Bill

Hi @Raissa Nepomuceno Epaminondas I recommend first extracting all the accountId values from the relevant calls into Created Variables to consolidate them, and handle any nested list problems. Then, using split() back into a list before adding the distinct function. Regarding your requirement to "If ALL users are inactive,…

Hi @Kellie Mingus Has your team / org changed the work item hierarchy? If so, please see this open JAC defect for that symptom: https://jira.atlassian.com/browse/JRACLOUD-96959 Kind regards, Bill

Hi @KC Wong Sigh...I have noted dozens of these posts in the JAC items I follow in the last 5 days. Looks like the keepers-of-JAC need to implement bot detection, account banning, and comment deletion automagically. It is a tricky problem as Atlassian likely wants to still allow free-licensed people to participate in…

Hi @Anthony Pugliese Does the user for the API token in the rule action have permissions needed for that project / space? If not, please try with a different user's API token. Kind regards, Bill

Hi @Sridhar Gandla Would you please provide more context for your question? That will help the community provide better suggestions. In your context, please include any automation rules you have already tried and why they may not be working as you expected. Until we see that information... * Releases / Versions have built…

Hi @Mugilan Sukumar What is the source of the information you posted? There is no JQL function overdue() in Jira, built-in features. Kind regards, Bill

Hi @deseymour Before we do anything else, let's check if the rule is "glitched". That can happen from too many edit / publish cycles where the behind-the-scenes stuff gets corrupted. To test that: * disable your current rule * recreate it from scratch * re-test If that does not help... Are you getting that same error where…

Hi @Kenny Stevens -- Welcome to the Atlassian Community! The workaround I described is the only way for many cases. For the special case of only one-attribute in the results, you may use a simpler approach with the source list to create a Dynamic Lookup Table, and then use the get() function with the table. For non-trivial…

@Sandy Greenberg -- Sorry for the delay in responding as I was offline for a bit. If the sample file you show has that error /symptom and all of the choices are valid options (including "All Major Platforms"), I do not know what would cause this. If you are on a paid license level, I recommend working with your Jira…

Hi @sravani vennapusa -- Welcome to the Atlassian Community! What problem are you trying to solve with this measurement? That is, "why do this"? Knowing that may help the community offer better suggestions. Until we know that "why"... The measure of total duration from Created to Closed / Completed is called the "Lead…

Hi @Ganea_ Merissa First, when you use {{issue.duedate}} like that it converts the date / time object into the long format of jiraDateTime as text, and thus will never match what is in your First Value of the condition. To force the comparison to work, add the matching format with {{issue.duedate.jiraDate}} Next, the…

One more thing to check... You show an image of your CSV file in some spreadsheet tool. When you view the plain text of the actual CSV file, does it contain None values for the empty ones, or nothing (i.e., just the comma separators)?

Hi @Sandy Greenberg -- Welcome to the Atlassian Community! I just tried a CSV import with both partially selected and no selected options for a multiple-select option field and that worked for a Company-managed, Software project where the field was global / company-managed. Perhaps you have a different configuration…

Hi @Varvara Krylovich -- Welcome to the Atlassian Community! Would you please explain what you mean by "automation rules are not available from project board"? In the images you show, the manually triggered rule named "Test epic" is present. Kind regards, Bill

Hi @deseymour Well, that is a different error...seemingly because that subtask type is not setup in the project. Some follow-up questions / requests are: 1) Please note in the audit log for the first, Create Work Item action for the Task that no issue type was selected. What value did you use in the dropdown for that…

Hi @Anupama_Karve -- Welcome to the Atlassian Community! The 1700 usage limit applies to a Jira, Standard license level. There are additional limits for different products, such as JSM, JPD, and Confluence. And, usage limits are higher / calculated differently for Premium and Enterprise license levels. To learn more,…

Hi @Isabella Merlo I believe the feature to view subtasks under a parent work item from the backlog view is only available with Business spaces / projects, and not others (e.g., company or team-managed software spaces / projects). Here is the JAC suggestion to add that feature, which you may watch / vote for to see…

Hi @Arnaud Brons This is a long-standing defect, and here is the most-recently closed / timed-out JAC item I found for it: https://jira.atlassian.com/browse/JRACLOUD-91255 My hypothesis is the JQL parser does its Boolean, order of operations checks and removes what it detects as the unnecessary parentheses...but not all of…

Hi @Joed Lopez For Jira Cloud...at the top-right of the page, select the question mark ? and then Give Feedback. Kind regards, Bill

First, let's try the smart value way: * in that parent field for Create Work Item, type in the smart value {{CEDARSSubtask}} * when it appears below the field, select it * navigate off of the rule action to save * test it There are a few fields like this in rules where they accept a smart value, and it is not obvious how…

Hi @deseymour In the image you posted, I see "Parent work item" noted as a field to enter. Is that the one you are looking for? Kind regards, Bill

Hi @Timothy McKay -- I essentially provided an outline of all the rule steps. What have you tried thus far to implement the rule?

Hi @Timothy McKay You could use an automation rule, triggered on a change to the field and which tests the field with a condition before sending the email. To get you started, please see this documentation: * https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation *…

Thanks for trying that, Erica. After a bit of digging, I found a related JAC defect / suggestion for this symptom indicating a problem with the API token...and a misleading error message problem: https://jira.atlassian.com/browse/JRACLOUD-82932 So, the only other two suggestions I have are: * create a new API token, encode…

Hi @Laurie Leclerc -- Welcome to the Atlassian Community! Have you tried using the Pull Request Merged trigger, and following that with a Lookup Issues action with JQL, checking the development status information: https://support.atlassian.com/jira-software-cloud/docs/jql-developer-status/ I recall others using that method…

Hi @Andrew Kelly As an Atlassian team member, you have posted this same content in at least three locations. If a non-Atlassian person did this, the community managers would remind them to select one location and post there, and then delete the duplicated content. Here are the locations: *…

Hi @Jamie Scott Please note in the flow of your rule, started manually from a page, that it: * deletes the current page * creates a new one * and then attempts to use Rovo to update the current page But, the current page is gone now...and do not believe Confluence rules have a branch to most-recently-created-page. Have you…

Okay, let's try this... Automation rules can get "glitched" by too many edit / publish cycles. This breaks them behind the scenes, causing weird symptoms and errors. The way to check for that cause is: * disable this rule * create a new one from scratch, entering just the minimum information to call your REST API endpoint…