Bill Sheboy Expert

Sorry I wasn't more clear...Your first parsing of Labels is still going to produce a list result, and so that needs to become text (a string) before using substringBefore() or maybe remove() Perhaps like this: * Create a variable, storing the result of your first parsing on "app_". Let's call it varApps * That variable is…

First thing: you appear to need a global/multi-project scope rule and you also appear to be on a Standard, Jira Cloud license. That means each triggering of this rule counts against your monthly limits. Take head that however you build your rule it does not exceed the limits, and so stop rule processing. For example, if…

Hi @Sinisa Glusac -- Welcome to the Atlassian Community! First thing, I recommend posting a new question and linking to this earlier one. Otherwise only the people following this older thread will see it and make suggestions. Thanks! Next, context is important for using the advanced edit for JSON. For example, the…

Sol, well done troubleshooting and combining your rules! And, as you are using global rules, I strongly encourage adding a global rule to watch for SLA/usage thresholds. This can help detect when you are approaching your execution/processing limits and perhaps email the site admins for action. The trigger to use for that…

Two things to consider: First, I recommend using the if/else condition syntax as that will help shorten the rule and make any errors more obvious. when something does not match. For example, adding a final ELSE to indicate an unexpected problem/match. Next, I note you are using the "between" test for the condition, which…

Thanks for clarifying, John. You could create a filter for your items, save it, and subscribe so it sends an email just before the sprint closes. For example, let's assume you have a two week sprint, this might help: project = myProjectName AND assignee WAS currentUser() DURING ( startOfWeek(-2), endOfWeek(-1) ) AND sprint…

Awesome; I am glad to learn that worked. Short version on Re-fetch: it reloads the data for the trigger issue at some point in a rule. Longer version: Regarding the Re-fetch action, the primary use is when an issue's data changes in a rule, and you need to use the changed values later in the same rule. For example in this…

Hi @Sol Yes, and...to John's suggestion: Please note the comments smart value is a list, and that John shows a check on the last one added. It is possible your condition is trying to match on a different comment body, so please try {{issue.comments.last.body}} or using the change log for the specific changed value. Kind…

I am glad to learn you got that to work. One more thing to try if you still want the name attribute: The Issue Created trigger can start the rule before all of the data is available. This is a known timing issues for Jira Cloud. The work-around is to add a Re-fetch action immediately after the trigger. This will slow down…

Hi @Lydia Roth Perhaps it is the use of fields, which usually is not needed with {{issue}}. Smart values are structure, case, and capitalization-sensitive, so please try using this instead for Start Date: {{issue.Start date.format("MM/dd/yyyy")}} When in doubt what will (or won't) work for smart values, please try the…

Hi @Alis-Hathway Ward (DO NOT USE) I just retested this one and it works for Jira Cloud when the context is an issue and the project has an assigned Project Category. Otherwise it returns null. {{issue.project.projectCategory.name}} Kind regards, Bill

Hi @Jeanne.Schiller -- Welcome to the Atlassian Community You could use JQL functions to find the linked epics, loading them into a Lookup Issues action, and then use smart value list filtering to find if they are all done. Here are the relevant links for those features: *…

Hi @Alis-Hathway Ward (DO NOT USE) You could try to access the field from the issue to see if it is available: {{issue.project.projectCategory.name}} If it is not available, you could instead call the REST API to get the project information. Kind regards, Bill

Hi @Lukas Without seeing the specifics of your rules, my suggested answer is: maybe. Let's assume you have two rules: * one is calculating the Residual Risk Score, and * another is triggered on a change to Management Approval Necessary, to then create the subtask If you do actually have rule #1 to calculate the score,…

Hi @Vaishnavi Sharath -- Welcome to the Atlassian Community! For a threshold counter like this, you may need to implement this yourself using a custom field and an automation rule. For example, creating a rule triggered on the issue being commented, and... * if the comment is from a customer, reset the counter to 0, * else…

Hi @Rajesh Shetty -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? As Nic notes, automatically adding work to an in-progress sprint will have unintended consequences...such as reducing your team's confidence/predictability of sprint planning to deliver value. Kind regards, Bill

Hi @Joseph Hani I see you have solved your question, and I wanted to ask... Did you intend the Initiative's percentage value to be the average of the Epics' percentage values, or the actual indication of progress? Those values are not the same thing. If you want the actual, instead please consider calculating: (Total count…

Hi @Ellis Coon First thing, I am assuming that you are trying to automatically assign issues *before* sprint planning, and that during sprint planning the team would make adjustments based on capacity. On to your question... There is an open suggestions to add a "sprint updated" trigger, which you may watch/vote for to see…

Hi @Violetta When recommending a marketplace vendor product, please ensure that you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines for Marketplace and Solution Partners…

Your JQL could be something like this in the rule: project = myProjectName AND parent = {{triggerIssue.key}} AND issueType = "Mitigation task" AND statusCategory != Done Try using that with the Lookup Issues action to return the issues. Then check the size of the results: {{lookupIssues.size|0}}

Hi @jeanine -- Welcome to the Atlassian Community! As you note, the labels smart value is a list, so you can merge everything together, and then parse, or filter first. Two of the ways to solve this are: * use your current smart value, and then only grab the part before the first comma with…

Hi @Kara Nadarajah The board filter determines what is visible in the backlog, on the board, and on the reports. In addition for Scrum boards, the assigned sprint for issues further impacts the, backlog, board, and reporting. Looking at the board filter you listed, your "closed" issues would need to be in open sprints to…

Hi @John Thomas -- Welcome to the Atlassian Community! First, reporting like that is not supported with out-of-the-box features of Jira Cloud. Specifically, built-in reporting and searches are on issue data; they cannot find the absence of information, such as "0 found..." Next, what problem are you trying to solve be…

In that case, I recommend using JQL to find the subtasks of the types you want to count, and with the same parent of your trigger issue, storing the results with a Lookup Issues action. Then you can still use the size function to count how many are found.

The smart value for an issue's subtasks is {{issue.subtasks}} and that is a list attribute. And the size function can be used on that list to check how many subtasks are present. I recommend adding a default value of zero to handle when there are none in your condition test. {{issue.subtasks.size|0}}

Please change... {{/changelog.customfield_10052}} to {{/}} For more information, please see these examples from the documentation on lists: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#Combined-function-examples

Hi @Lukas How are you determining "issue approval": status transition, a custom field, something else? However you are doing that, you could write an automation rule with a scheduled trigger to check your various conditions and then send the notification. I recommend mapping out this process better before you start; that…

Hi @Michael Voronkov JQL helps to search for issues, which you can clarify in your search with more criteria. What it cannot do is find the absence of information, such as: "show me Bill's name if he was not assigned to issues..." If you need such reporting for a Jira dashboard, please consider trying: * record what…

Hi @Inna S I do not believe that is possible with out-of-the-box Jira Cloud. There are several open suggestions to enable configuration of those fields, such as this one: https://jira.atlassian.com/browse/JRACLOUD-36490 Kind regards, Bill

Hi @Inna S In my opinion, there are definitely gaps in the information and reliability of the built-in admin logging of events with Jira Cloud. For example some of the site admin actions in the log do not indicate who performed the action; some are not logged at all. Until these functions are improved by our vendor, some…