Bill Sheboy Expert

Hi @Holly A -- Welcome to the Atlassian Community! No, that is not possible with the built-in features of Jira. Although you could use an automation rule to gather the linked issues, and their comments, it would likely run into limitations for the number of items and it could not interleave the comments by date / time for…

Hi @Jason Garcia -- Welcome to the Atlassian Community! That gadget is a marketplace addon from Stonikbyte, not a built-in Jira feature. Please follow up with their support from the marketplace: https://marketplace.atlassian.com/apps/1216564/great-gadgets-for-jira-cloud-agile-charts-reports-kpis?hosting=cloud&tab=support…

Hi @Cash Coyne I recommend using the steps from the how-to article for finding smart values, looking at an example issue, and that will indicate the correct smart value path you need. The steps are: * identify an issue which has your field(s) * call a REST API function with a browser to search for your issue:…

Hi @Randy Elias A couple of things to try to prevent the duplication are the use of the change log (i.e., fieldChange) or condition checks: Try using the Change log The {{fieldChange}} smart value has some extra attributes which might detect the added / removed values from the checkbox, as the selected values are…

Hi @catenas -- Welcome to the Atlassian Community! 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…

Hi @Antigone K What problem are you trying to solve? That is, why do this? Knowing that may help the community to offer better suggestions for that problem. Thanks! Kind regards, Bill

Hi @Web Mobile That appears to be a marketplace addon / app and not a built-in Jira feature. If so, I recommend first looking at the vendor's documentation to determine if automated start is possible. If it is, then check if a custom field or a REST API call is used to start it. In either case, an automation rule might be…

Hi @Dean Milenkovic -- Welcome to the Atlassian Community! First thing: the Epic Name field has essentially been sunset, replaced by using the Summary. Are you still trying to use the old field? You have quite a few questions there, and they cannot all be answered using one automation rule. 1. If the Epic Name also…

Thanks for that information. A couple of more things to try: First, is that Team field single or multiple select for the issue? The JSON syntax is different if this is multiple select: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-select-custom-field Next, have you tried to…

Hi @Aswathi D Yes, using the built-in control chart report: https://confluence.atlassian.com/jirasoftwareserver/control-chart-938845628.html Note there are some limitations with this report, such as when there are a cluster of issues for a particular time measure and when the y-axis rescales, etc. Kind regards, Bill

Hi @Osama Al-Areky To learn who / what is transitioning the issues back to the other status, please review the issue history for one of them to see what happened. Also, I note you are only showing part of your rule. Would you please post: * an image of your entire rule...in one image, * an image of the rule details, at the…

Hi @Julie Li What problem are you trying to solve? That is, why do this? Knowing that may help the community to offer better suggestions. Thanks! Until we know that... Mentions in Jira comments, text fields, etc. are represented internally this way: [~accountid:some user's account ID] That information could be used with…

Hi @Serge Calderara I am unclear about your question; perhaps you could clarify what you mean by "a kind of definition of done". That may help the community to offer better suggestions. Until we know that, some common definitions of such terms are... A definition of done for an agile team is a stable, agreed upon list of…

Hi @Anna Chilińska How actively do you want to manage this level of user change? I ask, because a Jira Admin can update roles / access such that only the Jira Admin can add or remove user access. Then any invite requests will send a notification to Jira Admin(s) for action. There is no need for additional automation to do…

Hi @Térence LECROIX Short answer: I do not believe that is possible, even for an individual Jira issue. A mitigation may be to accurately document your rule usage, such as in Confluence, to track which issue types teams anticipate could be impacted by rules; then use this documentation with the Global Rule Usage data to…

Hi @jovanio_junior Adding to John's suggestions...There are several open defects for that symptom, including these: Unpredictable results for filter searches with the [same] name https://jira.atlassian.com/browse/JRACLOUD-78819 Saved Filters not showing up in Filter Search (View all filters or Gadgets) when…

I am glad you have it working now. FYI...Your rule is using the Issue Created trigger, and that one can fire so quickly that some issue data may not yet be available, leading to problems and unexpected error messages later in the rule. The work-around / fix for that is to always add the Re-fetch Issue action immediately…

The image you are showing is not a view of the Releases page from the project. Please navigate to your project, and the Releases page (from the left of the page) and you will see the release ordering. That may explain why the function is returning no issues: it may be matching to another version than what you expected.

Hi @Steve Nienaber To confirm you are using this JQL function as documented: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#earliestUnreleasedVersion-- The "earliest" unreleased version is the one at the bottom of the version list, when viewed from the Release page. It does not use any date fields…

Hi @Ceil Francisco -- Welcome to the Atlassian Community! 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…

There is a rule Log action which allows writing any value to the audit log when the rule executes: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html#Jiraautomationactions-logactionLogaction Writing the variable to the log will help identify what is happening.

Are you trying to add the fix version from the trigger issue? For the rule image you show, the edit action is referencing {{issue.fixVersions.name}} inside of the branch to the linked issues. And so {{issue}} then refers to the linked issues as they are looped over. Essentially the rule is setting the fix version to the…

Hi @Priyadharshani Pandiyan I am not using JSM and would not know which queries to suggest. Some of the things you ask seem to be in the built-in fields, so perhaps look over the Advanced JQL reference for JSM to see how that helps: https://support.atlassian.com/jira-service-management-cloud/docs/jql-fields/ Kind regards,…

Awesome; I am glad to learn that worked for you! I believe the bulk-handling of {{issues}} for Jira Server and Data Server handle all of the fields, but Lookup Issues only handles a few currently for those Jira versions. When that action was first added for Jira Cloud, it only supported about a dozen fields, and about a…

Hi @Gil Does the scheduled trigger for your rule have JQL? From what you describe, it probably should not when you want to send a single notification: then the notification can come from the Lookup Issues result. Rather than use a separate condition, have you tried using JQL with your lookup to compare your custom field to…

Hi @Fabien I recall the advanced roadmap fields are not fully supported by automation rules, and the custom field id value may be used, rather than the field name, in an advanced edit with JSON. Please use this how-to article to determine your Team field's custom field…

Hi @Alex What problem are you trying to solve? That is, why do this? Knowing that may help the community to offer better suggestions. Thanks! Until we know that... The information about status transitions is stored in the changelog, and that is not easily accessible by automation rules. As @Hana Kučerová suggests, the rule…

Hi @Tobias Schweiger -- Welcome to the Atlassian Community! First thing: I am not using Confluence automation rules and so my suggestions are based on what I know about Jira Cloud automation features. Please verify / test what I suggest to learn if it can work with Confluence automation. With that out of the way... * Does…

Hi @Mahesh Swaminathan I recommend not changing an issue's type with an automation rule. Instead, consider cloning the issue to the new type and the abandoning (or deleting) the original one. Changing an issue type may lead to field, workflow, and other challenges. For this reason, Atlassian has a specific function in the…

Hi @Sonal Detection of Insight changes (and access to their information) is not supported for automation rules yet. Please see this post in the JPD community area for more information: https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Automation-rule-for-new-Insight-input/qaq-p/2268114 Kind regards, Bill