Bill Sheboy Expert

Hi @Gaurav Arora In addition to the suggestions from @Dave Mathijs ... How often do you need to perform a query like this and how much money / effort are you willing to invest in it? * Need this one time...* Export all of the issues for the month of interest, and use spreadsheet functions to extract the time from the…

Hi @Kevin Chiu -- Welcome to the Atlassian Community! In addition to the open feature suggestion that @Mohanraj Thangamuthu noted... Have you considered disabling automatic / default assignees for your issues? This would immediately stop the extra notifications, allowing your automation rule to perform the "inherited…

Hi @Nur Fatin Adding to Valerie's suggestions... It is generally a bad idea to delete issues in Jira Cloud without a very good reason. There is no "undo" capability to reverse the action. Worsening this risk, deleting from an automation rule could lead to rapid loss of issue information. Instead consider moving such issues…

Hi @Caroline Turner -- Welcome to the Atlassian Community! First regarding the "error" you observe in the log, that is indicating one or more issues did not match the condition. Have you checked the status of the issues which did not match for all link types? Next, with a Jira Automation rule, there is no way to pause…

Thanks for that information. As written, the trigger will only select the issues that have changed since the rule was last updated. You may update the JQL in the trigger to add the other conditions to it. I recommend also adding your project(s) to the rule to limit the scope. project = yourProjectName AND updated <= -7d…

Well done thinking of the different cases! They would be this: * empty value => non-empty value * non-empty value => a new non-empty value * non-empty value => empty value You could use the current value and {{fromString}} to test with if / else conditions and handle the paths needed.

Hi @Jeremiah Rappley -- Welcome to the Atlassian Community! My mistake as I am currently not using Confluence automation rules: one may trigger or branch on CQL to Confluence pages but not use Lookup Pages with CQL. As a workaround you could call the REST API content search with CQL and the Send Web Request action. Here is…

Hi @Florian Wehner You describe your customfield_11069 has a list of days of the week. Is it a single-select, option field? If so, please change your parameter to explicitly use the selected value. Otherwise I believe the default attribute returned is the id, such as 1, 2, 3... issue.customfield_11069.value Kind regards,…

Again I suggest: please use whichever values make sense for your team, depending if the states are "working" or "waiting". You and your teammates will better be able to answer that. The people in the Atlassian Community are not on that team, and so we would be guessing or answering based on our own processes / workflows.…

Sadly, Jira Cloud does not have built-in functionality to manage stuff like working / non-working assignment for people who are in / out of office. Such features are more in the space of service management projects. I recall an earlier question related to this, and the limitation was: a dynamic user-list could not be…

Which version of Jira Data Center are you using? I believe the Lookup Issues action was added in version 9.0 https://confluence.atlassian.com/automation/jira-data-center-automation-release-notes-1018767858.html#JiraDataCenterautomationreleasenotes-9.0.0-9.0.19.0.0-9.0.1 That is also when the Create Variable action was…

Here is a how-to article for calling a REST API endpoint from an automation rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828

Hi @Ratom Here is the documentation for moving issues to / from the backlog for Team-managed projects: https://support.atlassian.com/jira-software-cloud/docs/enable-the-backlog/#Move-issues-from-the-backlog-to-your-board Kind regards, Bill

@Leo Gonzalez please try to stay in one thread when responding. That will help others reading this question in the future know if there are multiple possible solutions. Thanks! Please post an image of your rule trigger, showing the JQL and option for including issues that have changed since the last time the rule executed.…

Hi @Jiei Hara -- Welcome to the Atlassian Community! Jira's scrum boards consider issues "completed" when they are in the rightmost column of the board. All other issues may be carried forward into the next sprint, or backlog. I hypothesize your "Cancel" status is not mapped to that column and only "Done" is. To solve…

Hi @Paul Clarkson -- Welcome to the Atlassian Community! There was a symptom related to this behavior a few weeks ago, apparently related to the UX changes and those new, annoying "issue updated..." messages: https://jira.atlassian.com/browse/JSWCLOUD-27351 The defect indicates it was fixed two weeks ago. One way to check…

Hi @Leena Siddamshetty Short answer: because solutions for this are complicated and risky, perhaps consider ignoring the historical issues and only set the "Last Comment DateTime" field for newly added comments. To do what you ask, the rule would need to: * iterate over the comments in an issue, * filtering to remove those…

Hi @Lori Milam If your rule is triggered on a change to the field, you could try using the {{changelog}} smart value and test if the {{fromString}} is not empty. That would indicate the value changed. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--changelog-- If this does not help, please…

I believe that is the suggest format to add to rules, and it does not work yet, to the best of my knowledge. The workaround is to add each user in the team as a separate mention.

You will need to review the REST API documentation to learn that in detail. For Confluence page updates with automation rules, the general flow would be: * capture the page id information after it is created * use one call to get the page's content, loading it into the web response smart value * use text functions to…

Did that resolve this one for you? If so, please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @Marcelo da Paz Pinto -- Welcome to the Atlassian Community! If you are using a JSM form, the smart values were recently made available for such forms: https://support.atlassian.com/jira-service-management-cloud/docs/access-smart-values-for-forms-and-form-fields/ You could use the Create Confluence Page action in your…

Hi @Fouad El-Gendy I do not believe that is possible with the built-in automation Send Slack Message action. Instead you could try to save the original message information (or find it) and then reply-in-thread with the Slack REST API, called using the Send Web Request action. Kind regards, Bill

Hi @A A Ron Geister _Trundl_ Here is one of the suggestions to add that feature to rules: https://jira.atlassian.com/browse/JRACLOUD-80134 Kind regards, Bill

Hi @Jeremiah Short answer: Please use whichever values make sense for your team, depending if the states are "working" or "waiting". I do not believe the differences in Status Category values matter for Jira reporting as the field has little-to-no impact on workflow, measurement, etc. within Atlassian tools. When one wants…

Awesome; I am glad to learn that helped! Is it all working now? If so, please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

There does appear to be a configuration problem with the project. As the field is on the page, that is not the cause...unless there is a duplicated field. I recommend working with your Jira Site Admin to contact Atlassian Support to take a look: https://support.atlassian.com/contact/#/ When you hear back from them, please…

Hi @Harrison Ponce Regarding issues moving to / from the Backlog view, there is a difference between Company-managed (CMP) and Team-managed projects (TMP): For CMP, the issue Status and mapping of Status values to the Board does impact when an issue shows in the Backlog versus on the Board (or neither for completed issues…

Okay, let's go "brute force" to solve this: two rules, one for create transitions, and one for non-create transitions. 1) Create a rule, triggered on Issue Created, and check the status with a condition. Then check existence and perform the clone. 2) To fix the rule triggered on Issue Transitioned, let's return to your…

Thanks for that information, @Eoin As the root cause has not been specifically addressed yet, I suggest adding a note to your article about possible performance issues and how to disable the feature. That will mitigate the possible increase in customers submitting support tickets for the symptom as they try the feature.