Bill Sheboy Expert

Hi @Massimiliano Stretti Although it is unclear what problem you are trying to solve by adding the linked issue data to the Description field...you may search for issues by link type with JQL: https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Issue-link-type Additionally, you may search for issues with a…

Hi @Paolo Garofalo In addition to the ideas Stephen suggested to make the rule trigger more specific... Have you checked if someone enabled the "Allow Rule Trigger" option for this rule in the details at the…

Just to confirm what you are observing: * when a rule uses a Scheduled trigger with JQL and references {{issue.Program Owner.displayName}} there is a value, but... * when a rule gets the issues from a lookup issues action the smart value {{lookupIssues.Program Owner.displayName}} does not for the same Jira issues? Again,…

Hi @MARY USEN Yes, I believe it is possible to clone an issue into a dynamically identified project, and it is more complicated than a normal issue cloning. First, what I believe will not work with automation rules... * Project-scope rules can create issues in other projects (e.g., your DEF example) but the Clone Issue…

Hi @Marcia Booth I do not believe that is possible, however... If you look at the top navigation bar under Filters, your starred / favorites will be at the top. Kind regards, Bill

As your first rule is triggered by the linking, it cannot also remove the flag: the triggering event is different. For your second rule, you do not need to use the destination issue from the first rule, as the branch can be used instead to find the issue with a condition on Flagged: * trigger: transitioned to Canceled or…

Awesome! Was the rule multiple-project scope, and removing that project fixed it?

Awesome; I am glad to learn that is helping. Regarding the date forecasting, how about this: * find the current active sprint before the branch, assuming it is the latest one* use lookup issues with JQL of* project = myProjectName AND sprint IN openSprints() * get the sprint end date from the first issue in the results*…

Yup, that is the cause. Here is an example suggestion / defect for that symptom: https://jira.atlassian.com/browse/JRACLOUD-72282 The work-around of creating separate reporting for CMP and TMP is likely of no help for your scenario. I recall community posts about using marketplace addon gadgets which group on the value…

Hi @Celina Kim My observations and questions for this one are... 1) That is a curious error message, as it seems to indicate the rule has multiple-project scope, but the log's Scope column indicates it is for one project. What is the scope of the rule: project, multiple-project, or global? 2) Is this a company-managed or…

Hi @Jeevan Kumar K G What have you tried to solve this problem / need? If you have written an automation rule which is not working as expected, 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…

Hi @Jason Boyle -- Welcome to the Atlassian Community! How are you generating this report? For example, with an JQL issue search? And...are any of your teams using team-managed projects (TMP)? If so, that could explain this symptom as each project has its own instance of the Status values, even when they have the same…

Awesome! And with the migration to Cloud, get ready for "the gift that keeps on giving [admin headaches]": team-managed projects ;^)

Please let me know if there is something specific about it you would like me to try to explain. The "tricky" part with link-related rules is often the link direction. Thanks!

Hi @Kamil Askerov Would you please clarify the symptom you are observing? And please include an image of the audit log details for when the rule does not work as you expected. For example... Do you mean the specific attachments added with the comment are not the only ones copied to the linked issues? If so, that appears to…

Hi @Samuel Kolloch First thing, would you please clarify what you are trying to do? As written, your rule would log the complete total for all child issues of the epic, every time work is logged. That may not be what you wanted. Instead, the Work Logged trigger could be used to only add the new information to the…

Hi @Rebecca Hylek I do not believe there is a built-in way to do that yet, and here is a suggestion to add that capability: https://jira.atlassian.com/browse/JRACLOUD-39724 If you have software engineering support from your team, you could use the REST API functions to edit the filters in a loop, as described in that…

Hi @Jack Brickey Based on the rule shown and inside of the Lookup Issues iterator, the issue prefix would not be used. Kind regards, Bill

Hi @Sien Xia What type of project are you using: company-managed or team-managed? You may find this information at the bottom-left side of the screen expanding area. And if using a team-managed project, is that a People-type field you have added? If so, many of the attributes may not be available to rules. This is a known…

Hi @Mithra Upadrasta, AnilKumar -- Welcome to the Atlassian Community! What is the problem you are trying to solve? That is, "why" do this? Knowing that may help the community to offer better suggestions. Until we know that... With the built-in features of automation rules, I do not believe you could include an image of a…

Hi @jose_aparicio Yes, and...to the ideas from @Jack Brickey and @motherg that there may be a better way to solve this, such as using custom filters and some issue indicator (e.g., issue type) to focus on bugs when needed for analysis. Regardless, it is possible in an automation rule to assign an issue to a specific…

Nice work, @Rebekka Heilmann _viadee_ Did your team of admins also check for old / broken automation rules...or ones with incorrect scoping? How about webhooks, email handlers, and addon apps (perhaps no longer used)? Kind regards, Bill

Hi @Helen I recommend creating a global scope rule with the Service Limit Breached trigger to notify your site admins of breaches: https://confluence.atlassian.com/automation/jira-automation-triggers-993924804.html#Jiraautomationtriggers-servicelimitbreachedServicelimitbreached With that trigger, the threshold may be…

The parent link field is essentially sunset, replaced by the parent field consistently across the issue hierarchy: https://community.atlassian.com/t5/Jira-Software-articles/Introducing-the-new-Parent-field-in-company-managed-projects/ba-p/2377758 Please update your rule's JQL accordingly and re-test. Next, have you…

Thanks for that information; I would first remove the newlines before trying the match. Please also note, the documentation states: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#match-- Note that "is based on" as it does not specifically indicate what does / does not work for regular…

Awesome; I am glad to learn that helped! Now that it works, I recommend reviewing it with your colleague so a couple of people on the team understand the rule. That will help with maintaining it in the future. Please consider marking this question as "answered" to help others with a similar need find solutions faster.…

HI @Solomon, Riyad, Vodacom Both of those scenarios are possible, and they will require a multiple-project or global scope rule. Project-scope rules can only create (or clone) issues in other projects, but cannot access or update them. Your Jira site admin will need to change the rule scope as such rules are managed in the…

Hi @Patrizia Heinzl No, but the work-around for that scenario is to lookup the id needed from the name: * call the REST API function to get all sprints for your board, using the Send Web Request action * filter the list by your name, and grab the id for use to set the field If you want to try that approach, here is a…

I do not know, and it would probably depend upon your usage scenario. How do you plan to query for worklog data? I suspect calling it for a single / few issues is no problem. You can call it from a browser or Postman if you want to try it and gather data on performance.

Hi @Tyler C -- Welcome to the Atlassian Community! With the built-in JQL, I believe that is the "started" date / time. That is, when the work was logged as "happening". To search by more criteria, I believe you will need either a marketplace addon / app or to call the REST API function, providing UNIX Timestamps for the…