Bill Sheboy Expert

Hi @Derek Knudsen Ignoring for a moment the idea of using story points on subtasks (which others may comment upon...) you can do this in several ways: * use Lookup Issues with JQL to find the issues meeting the criteria, and then sum * use Lookup Issues on all of the issues, and use smart value, list filtering, and a math…

Hi @Stephen Holt It looks like you figured out using a list iterator to get the values. Did you want to do something different than what you are showing? Kind regards, Bill

Hi @Troy -- Welcome to the Atlassian Community! Adding a new comment and editing an existing one produce two different events. And so there are two different triggers: Issue Commented and Comment Edited. You could clone your rule and change the trigger to cover both cases. Another option is to use the generic Issue Updated…

Hi @Guy Renko Although you can do what you ask in one step (using the text functions, including match), you are trying this in three edit issue actions...which is no problem. The challenge is automation rules use the issue data from the point the rule triggers. Even if you make a change saved out to the cloud, the value is…

Hi @Santhosh R Bhat Adding to Svenja's answer... On the issue views / pages, both of those fields are named "Story Points". The difference in fields is only relevant for configuration, automation rules, and calling REST API functions. Where are you concerned about using the correct field. Kind regards, Bill

Hi @Samuel Bar That does sound possible. What have you done thus far to solve this need? If you have started a rule and it is not working as expected...Please post an image of the complete rule, images of the relevant actions, an image of the audit log details showing the rule execution, and explain what is not working as…

Smart values are name, spacing, and case-sensitive. And the smart values available in rules often are different than the field name displayed in the UX. Thus it can help to first confirm your custom field id, or smart value, is supported by rules and the correct value to use. This how-to article can help. Essentially…

Hi @Ryan Schamp Probably "yes", and... As you are using a global scope, automation rule it can branch to any issue. You just need to identify that charter issue you mention and the data could then be used in your communications. I am not using the Deployment Successful trigger at this time, and so cannot test this. I…

Hi @Heath Holcomb That cannot be done at this time. Here is the suggestion to add this missing feature: https://jira.atlassian.com/browse/JSWCLOUD-25523 You may watch/vote for it to see progress. Kind regards, Bill

Hi @Peter van de Lageweg Sometimes yes and sometimes no...You essentially need to experiment with the functions to learn which ones can do this. And even then, context is important. For example, if there is anything which collapses to null in the expression, the entire thing will either collapse to null or raise an error.…

Hi @Aaron Howard Please use the Advanced Compare Condition when the fields you want to test are not listed in the drop-down fields of the basic Field Condition. That one allows you to specify a smart value expression. Kind regards, Bill

Hi @Adriana Domínguez Eguiarte I am curious: what problem are you trying to solve by doing this? That is, "why" do this? Card colors are shown on a board or the backlog. On the board, the cards are already in columns by their mapped status values, and in the backlog the status values are already on the cards. Kind regards,…

Hi @Ville Kylmänen -- Welcome to the Atlassian Community! Adding to the ideas from Tim... JQL cannot compare two different issue fields; it is not an actual SQL. You would need a marketplace addon for such comparisons. As a work-around...you may want to use automation rules, triggered on changes to either the Target End…

Ah...if there are two different teams please consider if there should be two different boards in the same project. Each would have its own backlog, board, and reporting.

Hi @Lyndl -- Welcome to the Atlassian Community! Would you clarify your scenario a bit? And have you looked at the articles describing this new feature of rules: * https://community.atlassian.com/t5/Automation-articles/New-Automation-action-Create-lookup-table/ba-p/2311333 *…

Hi @ideguchi.saori.2df -- Welcome to the Atlassian Community! If you have deleted an issue from Jira Cloud, it is gone. There is no "trash bin" from which to reclaim it. For this reason, some customers of Jira either disable issue deletion (and add an "abandoned" custom field to mark them) or purchase marketplace addons to…

Hi @Kaushik Bhattacharya -- Welcome to the Atlassian Community! No, that is not possible with the built-in burn charts. There are more configurable reports like this available in the Atlassian Marketplace. What problem are you trying to solve by doing that type of filtering? That is, "why" do this? Knowing that may help…

Hi @Nishant Rohilla JQL is not a SQL, and so does not have many such features. What that error is describing is the left-side expression must be a field and the right-side must be a value (and/or a built-in function of JQL). You are trying to compare two fields within the issue. Work-arounds for that need depend upon your…

In my experience, when refactoring and other "code smells" are addressed as part of daily working methods there is no need for separate work items to manage (or defer) such things. And it reduces "spirited conversations" of assigning story points to such types of work items. Any ways... You describe a flow to "get a…

Thanks for that information. Please post an image of a specific issue, showing the history where you have changed the Story point estimate value after your rule was enabled, on 10/12/23 9:28:54 pm. And then post and image of the audit log details if there were any changes after that point in time. Next, can you confirm…

Yes, and...to what Rudy suggests: I find the documentation is not always accurate on the casing of the messages provided. Consider forcing to upper (or lower) case before comparing. Writing the values from the trigger to the audit log will confirm this.

Okay, wow; that is a lot of fields to use in one decision, making me wonder about your use case. Would you please describe the problem you are trying to solve? And, describe an outline of the rule you are trying to do this? Until we see those... Please review the documentation link I provided for conditional logic. You…

Thanks for describing the symptom. The likely cause of this is the Issue Created trigger can fire so quickly that the data is not yet available to the rest of the rule. This can lead to conditions / actions / branches having missing data. The work-around / fix for this is to always add a Re-fetch Issue action immediately…

Yes, and...the behavior can be confirmed by writing that same value to the audit log just before (or after) those edits. That will show the increment of {{now}} to the second, as opposed to the Start Date and Due Date fields, which are only dates. One more thing...If this does not work, I recall a problem with using…

Hi @Khuram Khalil What leads you to believe the automation rule action is using the incorrect issue view? For a question like this, please also post the audit log details showing the rule execution. That will provide additional context for the rule execution. Kind regards, Bill

Kent, would you please show an image of your current, complete rule, and of the details of the edit issue action? Those may help explain this difference. Thanks!

Hi @Vilhelm Lundqvist -- Welcome to the Atlassian Community! To me, this sounds like a short-term need (hopefully!) and something to handle during backlog refinement and confirmed during sprint planning...before the sprint starts. If the team waits until after the sprint starts and then runs a check/report on missing work…

Hi @Brittany Montgomery -- Welcome to the Atlassian Community! One way to do this is with an advanced branch on whatever (or whomever) is the distinct criteria for sending the emails. That may work better than using the if/else structure for your scenario. For example...let's assume a user is the Reporter for multiple…

Arg...my bad as I answered too quickly: the labels are a list for this context and so that is where iteration is needed for your first version: {{#issue.labels}}"{{.}}"{{^last}},{{/}}{{/}}

Hi @Guillaume Govers When you tried Linked Issues and note that "neither of these is functional", what do you observe happening? I just tried linking ideas in two different JPD projects and it worked. Kind regards, Bill