Bill Sheboy Expert

Hi @Olga Videc Does your rule do / check anything else with the issues found in the released version? If not, perhaps consider this approach using a lookup to find the distinct System values: * remove the branch on issues in version * use the Lookup Issues action with JQL to gather the issues * use the distinct list…

Hi @Arpita Solanki For Jira Cloud, scenarios to send a single email per Assignee would use the Advanced Branch feature, but that does not exist yet for Jira Data Center. Here is the suggestion to add the feature, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749 Some…

Hi @Priyanka Agrawal and @John Funk For the table, you could use the markdown inside the iteration of the lookup results: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=tables Regarding the issue limits, Lookup Issues can return up to 100 issues to a rule. The new issue search REST API endpoint can…

Hi @Steve Krummes -- Welcome to the Atlassian Community! There are likely marketplace addon gadgets to display information like that, but nothing out-of-the-box. As a workaround, and if are okay adding a custom field, you could try an automation rule. * add a custom text field to the relevant project * add an automation…

Hi @Oliver Moore Are you trying to only match on the value attribute within the values list? If so, please try this: {{webResponse.body.values.value.match("(.*Content.*)")}} If instead you are trying to get the entire record from values where it matches, please try using list filtering on the value attribute to get the…

Hi @Derek LoGrande How many rows are in your table: just the header and one data row, or more data rows? If there is one-and-only-one data row, and the columns are stable, using the text functions would probably work...requiring some experimentation to get correct. If there are multiple rows, still with stable columns,…

Hi @VVC The current Edit Issue action for the Attachments field copies all of them, and there is no way to limit that. I recall some suggestions to make that configurable for Jira Cloud but do not know if there is also a suggestion for Jira Data Center automation. Here are workarounds I have read about, although I have not…

Hi @Brian Taylor If you try the JQL in the Lookup Issues standalone to test it with View All Issues, does it return any issues? If so, in which project(s) are the issues? If the issues are in multiple projects and the rule is a single-project scope rule it cannot "see" the issues. The rule scope will need to be changed,…

I understand your frustration as learning takes time and effort. Please note this is the Atlassian Community. It is a place for people with similar interests to learn and collaborate with each other and is not a place to provide free labor and turnkey solutions to requests upon demand. It is also not the Atlassian Support…

The trigger for field value changes only fires when an issue is updated. When you want the emails for Issue Created also, the rule will need to be duplicated to use that trigger. For an issue update which does not send the correct emails, you would need to research that for each case to determine the cause. Note that if…

Please read the documentation on the changelog / field change smart values. When the trigger is for a field change, the prior / removed values may be accessed for use in the rule. One challenge for your scenario is only the removed user's account ID is available. In that case, a call to the REST API will be needed to get…

My recommendation would be to review specific issues which do not work as expected, check their issue history and the automation audit log to understand what is causing the symptom. In my experience, when the workflow uses "All" for most of the paths and uses transition rules, it can be challenging to enforce a desired…

I understand the rule usage limits concerns, although for your scenario it could encounter other limits for a batch processing approach: * let's assume rules worked differently, and processed the scheduled trigger serially versus in parallel (which they apparently DO NOT :^) * in that case, each issue would be checked and…

In the related issues condition, you could try inverting the JQL to exclude the JSM project: project != yourJSMProject ... As that condition starts by checking the linked issues to a triggered JSM project issue, this would find any other issues in different projects. And, the rule scope will need to change from…

Hi @Zee Choudhry Interestingly, I notice this audit log feed for plugin activity is visible for a Free license site, even though the current site audit log is not available except at Standard license and higher. Will this continue to be available for Free license in the future? Kind regards, Bill

Hi @Verena Gisler There is no automation rule action to add a task to a page. A complicated workaround is using the REST API with the Send Web Request action: * use the REST API to GET the content for the page, including the task list within the HTML <ac:task-list> your task list </ac:task-list> * identify the last task ID…

Hi @Jeff OBrien There are built-in, Target Start and Target End global custom fields, and they are not currently compatible with use in Jira Product Discovery (JPD). Did you add other custom fields in JPD, perhaps with overlapping names? If those are custom fields added to the JPD project... Have you tried using a Field…

Hi @shriya For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches,…

Hi @Kris Dewachter Automation rule branches which could be on more-than-one-thing are executed in parallel and asynchronously, with each pass through the loop using separate process resources. A variable created inside of such a branch will not be visible outside, and even if it was visible, such branches are not…

Hi @Євгеній Єрін -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image for continuity, * images of…

Hi @amit_vickey -- Welcome to the Atlassian Community! Are you using the built-in, custom field type of checkbox, with multiple options? If so, your rule could use the Advanced Branch to iterate over the values, adding a subtask for each selected value. Please note with this approach you cannot predict the order of…

Hi @NoName What have you tried thus far to solve this need? If you have an automation rule that is not working as expected, note context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity, * images of any relevant actions /…

Hi @Bianca Palacio -- Welcome to the Atlassian Community! That symptom was added as a defect today in the public backlog. You may vote for / watch it to see progress. https://jira.atlassian.com/browse/CONFCLOUD-80974 Kind regards, Bill

Hi @Thomas P -- Welcome to the Atlassian Community! First thing: solutions for a scenario like this can be "brittle" because the ordering is dependent of fields which can easily / frequently change. Thus an automation rule would need to reorder the issues frequently. Please consider that before proceeding. With that…

Hi @Corey Hampton Excellent question, and... When JPD was released, they added a variation on issue linking with "Delivery Tickets" using the Polaris-type of links. These do not show up as generic issue links in the UX (and they do not fire the issue-linked event). Behind the scenes, these are the "implements" and "is…

What I put as LaunchTierCustomFieldID was a placeholder. Please replace that with your field: customfield_17213 Please note the values must exactly match, including case-sensitivity, for this to work.

Hi @Yi Meng First thing, this is a very old thread, and so I recommend creating new questions for such cases, and perhaps adding a link back to the older one for context. That will ensure the maximum number of people see it to offer suggestions. Next, when a created variable is converted with asNumber for inline math…

Hi @Cristóbal González That error is correct as the {{fieldChange}} smart value likely creates the invalid JSON. You could confirm this by writing the smart value to the audit log and considering what that would do to the JSON expression shown. What is the type of your customfield_17300 in the software project and what…

Hi @Clark Damron -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches, * an image of the audit log…

Thanks for that information, @Nancy Tinder Please try to stay within the same thread when responding. That will help people reading this question in the future know if there are multiple possible solutions. Thanks! Your scenario seems to be this: GIVEN there are open JSM incidents in the service project AND an incident has…