Bill Sheboy Expert

Hi @erik.riedasch -- Welcome to the Atlassian Community! That defect was marked as resolved on 7 March: https://jira.atlassian.com/browse/CONFCLOUD-80974 When I just checked, the links appear correctly on my test site. Kind regards, Bill

Hmmm...I do not recall that as a built-in one. Please post an image of the gadget as it appears on your dashboard.

Hi @Tim Bonney As this is a very old thread, I recommend creating a new question, and perhaps adding a link back to this one. That will ensure the maximum number of peoples see it to offer suggestions. In the mean time...clearing a checklist depends upon the type of field. When using a marketplace addon for checklists, I…

Hi @Gerrit Wahlers My understanding is asset data is looked up just-in-time, and the Edit Issue action with JSON can have timing problems by parsing too quickly...leading to missing data and errors. The solution for this is to first build that JSON expression and save it in a Created Variable, perhaps named varJson. This…

Thank you for that information. Your rule is not creating an issue, so do not use the {{createdIssue}} smart value. Instead use {{issue}} for your Send Email action. For example: Nova Ideia - {{issue.key}} - {{issue.summary}}

Hi @Roy -- Welcome to the Atlassian Community! There are known defects with math operations inside of list iterators, including date / time diff() within Lookup Issues iteration, where it uses the wrong fields in the operations. That can cause all kinds of problems! Please review these to learn how they align to the…

Thanks for those additional details, Owen! For a JPD project, doing what you ask would require two custom fields and two automation rules: * two custom fields:* one text custom field to store the date / time of the last status update; let's assume its name is StatusLastChanged * one number custom field to display your…

Hi @Stanislav Borisov -- Welcome to the Atlassian Community! After the Edit Issue action, please add a Re-fetch Issue action to reload the data before the condition tests the approvers. By default, rules updating issue fields update the database in the cloud, but not the in-memory copy of the issue the rule has. This is…

Hi @Francis Calderisi Atlassian automation rules cannot pause to show a screen, other than for the Manual Trigger to gather inputs before running the rule. If you do not find what you need from the built-in workflow validators, perhaps check the Atlassian Marketplace for addons of other validator types. And just to…

Hi @Abdullah Mohammed -- Welcome to the Atlassian Community! Are you asking about Atlassian Automation rules? If so... I do not believe that is possible with built-in features as there is no public REST API for rules yet. Here is the suggestion to add that capability: https://jira.atlassian.com/browse/AUTO-51 I have not…

Hi @Brage Mogstad -- Welcome to the Atlassian Community! I do not believe there is a public endpoint to access a Confluence Database's data yet. Here is the suggestion to add that feature: https://jira.atlassian.com/browse/CONFCLOUD-77328 Kind regards, Bill

Hi @Sarah Crown -- Welcome to the Atlassian Community! Which dashboard gadget are you using which presents a bar chart? And, is it a built-in one or from a marketplace vendor addon? Kind regards, Bill

Hi @Mark Corrigan -- Welcome to the Atlassian Community! Have you confirmed that the additional issue key you added exists and you have permission to access it? Have you confirmed that for the issues which are child issues of the newly added key, you have permission to access them? If so, I have never encountered a maximum…

Hi @Radhika K K -- Welcome to the Atlassian Community! You may find the ID values for the issue types in a project from the project settings for Issue Types (now called Work Items in some places), or from calling the REST API endpoint to get the supported types for the project. Kind regards, Bill

Hi @Mirmelshtein_ Roi Please try using the text functions to extract the email address, perhaps saving it in a Created Variable to make checking the value easier: * https://confluence.atlassian.com/automation/jira-smart-values-text-fields-993924863.html *…

Hi @Ethan Rennie-Degg -- Welcome to the Atlassian Community! Do you have permissions to create issues in that other project? Does the other project's issue type have required fields which are not possible to complete from the JPD view? Kind regards, Bill

Hi @Shmuel, Dave In my opinion, this is a long standing behavior / problem with the sprint date / time values, and is related to both the automated selection of the "start of day time" and time zones, and then putting those into a date field (rather than a date / time field). I hypothesize the feature is to support teams…

Hi @vaibhav bisht -- Welcome to the Atlassian Community! As others have noted, the Lookup Issues action for Data Center automation does not support custom fields yet. Here is the suggestion to add that capability: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 There are two possible workarounds, which are described…

Hi @Gowri Kumar Have you discussed this need with your Jira Admin so they can help set up the automation with the scope changes? Kind regards, Bill

Hi @Mark Adam [C] -- Welcome to the Atlassian Community! To learn the built-in issue fields, please look here: https://support.atlassian.com/jira-software-cloud/docs/jql-fields/ For your own custom fields, look at your project and example issues to find them, or ask your Jira Admin for help For more information about…

I thought you wanted that option enabled so the other rule creating the issue will trigger this one? Which is certainly okay; just gotta track down the problem. Based on the logs, there is something causing the issue-created event to be fired at least twice for the same issue, leading to the rule starting multiple times. I…

Hi @Benjamin White From what I recall about some community questions last year... After the changes to the Slack REST API requiring the use of apps for direct-messaging, I do not believe it is possible from Jira automation rule's Send Slack Message action. A user can be mentioned by Slack ID, but the feature to…

Hi @Mohammed.Kagzi -- Welcome to the Atlassian Community! Your expression has nested double-quotation marks for the startDate attribute. Rather than using the format() function, try the inline function, jiraDate format instead, or use format() without the outer quotation marks, adding them with the asJsonString function. {…

Yes: do not use the change log and instead please test each case as I noted earlier. * trigger: field value changes for Tags * condition: issue type is Story * branch: on current issue* condition: Tags contains Benefit Changes * action: send the appropriate email * branch: on current issue* condition: Tags contains…

Thanks for that info! And that is curious... First, please remove the filter at the top on ADMIN-9266 and check the log again to observe how that changes what you see...particularly how many rule executions happened after first triggered by the creation of ADMIN-9266. You may need to expand several executions to check…

Hi @Vinícius Pereira To provide more context for your question, please post: * an image of the complete automation rule in one single image for continuity * an image of the audit log details showing the rule execution, with all of the expand areas on the right side arrows > expanded Until we see that information: The…

Hi @chris sieverts I hypothesize as soon as there is a public REST API for automation rules and the audit logs, that will be possible: https://jira.atlassian.com/browse/AUTO-51 Kind regards, Bill

As written and with the "Check to allow other rule actions to trigger this rule..." option enabled, the rule will definitely trigger multiple times if the created issues are in the same scope as the rule. The questions are: which issue is doing so and does it perform any unexpected processing? For the two most recent…

Thanks for the additional information about your solution. FYI -- an article from Atlassian recently revealed the flatten function to help with nested lists. Perhaps try writing this to the audit log in order to merge the lists: {{lookupIssues.Systems.name.flatten.distinct}} For the data you show, that would produce this:…

Thanks for the updated information, and...for the issue shown in the log, RT-1, it seems that field is not available. Can you set that field manually from the Jira UX to confirm it is editable? Have you tried this how-to article to determine if the field is supported by rules for…