Bill Sheboy Expert

Hi @Mane Zakaryan Sorry I missed seeing your posts yesterday. Would you please confirm if your questions are answer or if something is still open? I ask because both of the threads are marked as "answer accepted" and I saw a note that you had resolved the issues. Thanks!

Hi @Odimar Tomazeli I recommend creating a new question for this one, and perhaps linking back to this one. Otherwise only the people following this older thread will see it, limiting the amount of community suggestions offered. When you post your question, please include images of your complete rule, showing details of…

Without seeing the details of your advanced branch, I am guessing a bit here... Having a sequential counter has be asked before, and the work-arounds depend on context / the structure of your branching. Specifically, what information from the {{webResponse}} do you need inside of the branch to create the issues? I have…

Hi @Amelia Hernandez -- Welcome to the Atlassian Community! I recommend simplifying that expression, as shown in the documentation: https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html Perhaps try this: The SecEng portion of your review has gone from {{#changelog.status}}{{fromString}}{{/}}…

No worries; we are all learning all the time! Would you please show the complete expression you are trying in the PUT data? I have done this technique before to dynamically update saved JQL filters, so I will look around to find my example to learn how I did it.

What you are seeing in the last audit log entry is from writing {{worklog.timeSpent}} and {{worklog.started}} to the log. However, my understanding is the {{worklog}} smart value is only relevant for the Work Logged Trigger: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--worklog-- I would…

Please note in the audit log that the Lookup Issues returned no issues. That is likely because the rule actor is the default of "Automation for Jira", and that is then used as the currentUser() in the JQL. Please try changing your Lookup Issues JQL to this and run the rule again: worklogAuthor = {{initiator.accountId}} AND…

Hi @JensH I noted in your question this: ...the list of new tasks comes from an external webcall where each object in an array should be created as new linked issue (before it was just a number i a field i could unroll). Without a loop construct in Jira Automation i cant see how i can iterate over the json array... With…

Hi @Danno If you run your JQL manually, does it have any results: worklogAuthor = currentUser() AND worklogDate >= startOfWeek() ORDER BY updatedDate DESC And, who is the rule "actor"? If it is the default of "Automation for Jira" it will likely not find any issues. If it is "user who triggered the event" it may find them.…

Hi @Mirela Todorova A couple of things to consider for those measures is: how do you want to measure them (by item, by average, etc.) and how often do you want to review them? With the built-in, Atlassian interpretation of a control chart and cumulative flow diagram, you can view averages (and sometimes individual)…

Agreed...perhaps consider teaching your product owner an idea from Mike Cohn: "estimate size; derive duration". That is, the team forecasts effort (as needed) and scheduling is a separate activity (as needed).

Hi @RXAVIER Before proceeding, I recommend checking if the Target Start and Target End fields are supported by automation rules. I recall earlier community posts that many Advanced Roadmap fields are not supported by rules. You can check this using this how-to article to confirm if the fields are supported for an example…

Please try different tables. Without seeing your fields, let me offer an example... 1st lookup table: tblLocation * key: beach; value: 30 * key: mountains; value: 50 * key: home; value: 20 2nd lookup table: tblActivity * key: idle; value: 0 * key: swim; value: 20 * key: hike; value: 70 * key: sleep; value: 10 Two custom,…

Hi @Jonathan Schwarze Your rule works as designed, and the challenge is the behavior of branches in rules: * Branches on one-and-only-one-thing (e.g., branch on parent, on current issue, etc.) get run in-line, as if the branch did not exist * All other branches which could be on more-than-one-thing (e.g. on JQL, linked…

Hi @Aaron Holt First thing, are you using "blocked" as a status and as a link type? If so, I recommend not using a "blocked" status, and instead using the built-in Flag feature to indicate blocking. I find when teams add a status for that condition (i.e., blocked) it becomes a normal part of their flow rather than an…

The power of lookup tables is "lookup". If you can get your values then the lookup happens in one step, without the looping or if/else structure you note. And once that happens for each field, there is no need for another rule: just add the values as needed. That was what I was describing earlier:…

Hi @Erica Hughes -- Welcome to the Atlassian Community! Yes, and...to Nic's answer: please see the diff() function to calculate the difference between the dates. And then you could use either if/else conditions or a lookup table to select your t-shirt sizing. To get you started on creating your rule, please refer to these…

Hi @David Blank I believe you are missing some parentheses in that expression if you want to match what the question asked. Thanks! Kind regards, Bill

Hi @Trudy P Claspill Yup: they changed their mind and "re-introduced" the feature. :^) https://jira.atlassian.com/browse/JSWCLOUD-25768 Kind regards, Bill

Hi @Arild Hoyland My hypothesis is the BCC field is not recognizing the separate email address, instead only seeing them as a single text value. Let's try splitting to create a list of values. Assuming your delimiter is "; " then please try this: {{emails.get("email").split("; ")}} Please adjust accordingly for your…

I am glad to learn this is solved, and... Hmmm...this sounds like your Jira admin person changed the permissions for the built-in Automation for Jira user...as that one should work for a simple, project scope rule. Or...the permissions for your project are very locked down and only specific named users are added for…

Would you please post images of your complete rule and the audit log details showing the rule execution? Those may help to explain why the subtask is not added. It is possible this is a timing problem, where the story is not saved fast enough for the rule to use it in the branch. A way to check that is after the action to…

My next suggestion would be to carefully use an automation rule to delete them, about 100 at a time, or so, by calling the REST API function: https://developer.atlassian.com/cloud/jira/software/rest/api-group-sprint/#api-rest-agile-1-0-sprint-sprintid-delete If they match a naming pattern, you could build that into the…

Please try this how-to article when you need to find the smart value or custom field id for a field. Essentially you identify an issue with your field, call a REST API function from a browser, and then search for the field in the results to learn the correct one for your site.…

Thanks for confirming, Mauricio and Darryl. Still no open defect for this in public backlog so the team may not know about it yet.

Hi @sreeram_anikodemahadevan -- Welcome to the Atlassian Community! You may force the conversion by adding the hexadecimal value to 0 in a math expression, like this: {{#=}}0+{{issue.MyHexField}}{{/}} Kind regards, Bill

Hi @Mayank Agarwal Have you used that board with the team yet? If not, I recommend creating a new board and deleting the one with the hundreds of sprints. Kind regards, Bill

Hi @david.meltzer Once the rule is inside of your branch to the parent, you can use {{triggerIssue}} to refer to the child issue. Inside of the branch, {{issue}} then refers to the parent issue. Kind regards, Bill

Hi @Natalia Mojica JQL is not a SQL, and so does not have the UNIQUE or DISTINCT constraints (or many other basic SQL features). (There may be marketplace addons for JQL to add some of these.) If you are trying to find issues in the current sprint, and which have not been carried over from prior ones, you could try this…

Hi @Mane Zakaryan Regarding linking the Story to the Epic, you could enter this smart value into the Epic Link field in the issue create action, rather than using the advanced edit with JSON: {{createdIssue.key}} That will refer to the epic created earlier. Regarding adding the subtask to the story, it appears you are…