Bill Sheboy Expert

Hi @Kerrie As Nic noted, that button cannot be configured. And you describe some of the team's workflow with build management and bundling of issues. Has your team considered trying the DevOps features / integration with your Jira project? That may enable using automation rules, triggered on the pipeline operations, to…

Hi @[deleted] -- Welcome to the Atlassian Community! Adding to Dave's suggestions... When you want to manage work across multiple teams, Jira has several things to help with that. For example, you could: * create a filter and board which spans all the Jira projects, treat that board as "read only" and use it for visibility…

Your rule has not used the Lookup Issues action, and so the {{lookupIssues}} smart value is empty. *** Did you check if you have the Lookup Issues action available? *** Regarding using the values, you wanted to edit the Epic to contain the min (or max) dates. And so when you are ready to edit the Epic the values may be…

Anne, let's confirm you have the correct smart value for your field... Smart values are name, spacing, and case-sensitive. And, smart values do not always match the displayed name of a field on the issue views. The how-to article below identifies supported smart values. Essentially the steps are: * identify an example…

I noticed your rule image, and my first suggestion should have been: try adding a Re-fetch Issue action immediately after the trigger. The Issue Created trigger can fire so quickly that the issue data is not yet available to the remainder of the rule (i.e., a race-track error). This can cause unexpected behavior the…

I withdraw my brittle observation as Atlassian just added this smart value to the docs in the last few days! https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--rule--

Hi @김영동 -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? That is, "why do this"? Knowing that may help the community to offer better suggestions. Until we know that... Using an automation rule to change an issue type is probably not a good idea. There are usually many differences…

Hi @Mehran Ahmadi Do you want to remove a specific text string from the beginning of the Summary field? If so, please try using the substringAfter() function, as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#substringAfter--String-separator- Kind regards, Bill

Hi @Dora Judith Martínez Vera For this scenario, identifying the correct "next" subtask to work on may be the way to solve this. If the subtasks have unique Summary values you could use a branch on JQL to find the correct issue for the assignment. For example, assuming the first subtask (the trigger issue) moves to your…

Hi @Sean Libera * How are you representing the completion of each of your 7 aspects of DoR? * And, what marketplace addons, if any, do you have for dashboard gadgets? Let's assume you are using 7 distinct Label values for each aspect, and you have no marketplace addons. In that case, you could try the dashboard, Filter…

Awesome; I am glad to learn that helped! Even though your question is resolved, that error seems to indicate a problem in the rule engine for handling this case with the Assign Issue action. You may want to submit a ticket to Atlassian Support to let them know about this behavior: https://support.atlassian.com/contact/#/

Please post an image of the audit log details (Show More) for when the rule runs. That may indicate what is happening. I recommend using a screen print, browser addon, or screen capture tool rather than taking a photo of the screen. That will make reviewing the image easier. Thanks!

Hi @Ivan Andonov There is a built-in Workload Pie Chart which does that. Is that the one you used? https://confluence.atlassian.com/jirasoftwareserver/gadgets-for-jira-applications-939939037.html Kind regards, Bill

Hi @Data Enthusiast -- Welcome to the Atlassian Community! That is a curious symptom and message in the audit log... I see you have added a Re-fetch Issue action to the rule. Are you doing that because the rule has more steps to perform (with the changed issue) or because of the known, timing problem with the Issue Created…

Hi @Kishore D What is the issue type of your child issues of the Epic? As written, your lookup issues action is using JQL to find any Epics which are children of the Epic. Instead I believe you want your JQL to use: issueType != Epic Kind regards, Bill

Hi @Claudia Gonzalez Arriagada The packaging model and rule limits have changed for automation, as described in this article: https://community.atlassian.com/t5/Automation-articles/Introducing-our-new-packaging-model-for-Jira-Cloud-Automation/ba-p/2446099 Please review that information to decide your next steps, such as…

Hi @May Azulay There are several possible causes for this symptom. Four of them are: * For the issue type you are copying to, the field is not selected for that issue type. Solution: work with your admin to add the field. * For the issue type you are copying to, the field is not on the issue views. Solution: work with your…

Hi @Sandip Bhosale -- 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…

Deanna, please see my earlier questions in the last post as they may help to improve your rule: * What is your Jira version? * Please post and image of the audit log details * Why using the Send Web Request action, rather than the built-in Send Slack Message action? * Please post an image of the body / content of your Send…

If you follow the link I sent, you will see the other functions for delete and archive on the left side of the page.

Hi @Andrea Rose There are at least two ways to do this check: * Add an advanced compare condition before the step you show, checking if there are any comments to process * To do this in-line with your existing rule step, using conditional logic and a math expression to check if there comments, as described…

What version of Jira are you using: Cloud, Server, or Data Center? Does your scheduled trigger have JQL at all? If so, please remove the JQL as it is not needed, regardless of the options selected for processing, bulk-handling, etc. And, the bulk-handling feature for the scheduled trigger and branches is only available for…

Depending upon your rule needs, there are two ways to do this with Jira Server: When you only need to view data, there is a bulk-handling feature of Scheduled Triggers and Branching. That does not seem to fit your scenario, but here is the documentation to learn…

Correct, I do not believe you need that step unless...there is a possibility of there being no issues in a release. If that is possible, what would you want the rule to do: still release the version, archive it, or nothing. If a release will always have issues, your rule can be simplified, dropping the first lookup issues…

Hi, Isabella. For your version of Jira, do you have the Lookup Issues action for rules? I asked that earlier and perhaps it got lost in ideas. If you have that action, you could: * use either a manual trigger (or scheduled trigger) to select the epics to update * use Lookup Issues with JQL to gather the child issues for…

Hi @Deanna Vazquez -- Welcome to the Atlassian Community! Does your scheduled trigger have a JQL statement? If so, the scheduled trigger will run the rule steps for each issue from the JQL. You may remove that trigger's JQL and only one message will be sent with the issues from the Lookup Issues action. If you are…

Hi @Tom Martinicchio -- Welcome to the Atlassian Community! For customers on a paid Jira Cloud license (Standard, Premium, or Enterprise) their site admins can create tickets with Atlassian Support here: https://support.atlassian.com/contact/#/ For free license customers, the community forums are the support system. What…

Earlier Anne noted the linked issue was in a different Jira project. That is why I suggested the rule needed a different scope. If all of the issues involved are in one Jira project, the rule only needs project-scope.

Unfortunately, I believe there are multiple "Team" fields in Jira for the various products, and some are single-select. That leads people to add a new custom field for what you asked.

Hi @Inna S The smart value for the rule's name while it is running is {{rule.name}} Without seeing the specifics of your scenario, I can anticipate using this smart value, as you describe, will both increase the length of rules and may be brittle for maintenance. (Brittle, because I do not know if this is a supported smart…