Bill Sheboy Expert

I am glad to learn you got that to work...And, I have not had much success with the Related Issues Condition, so I normally stick to either JQL ones or advanced compare on specific issue/lookup issues fields. The issue (no pun intended :^) with the related issues condition seems to be context-related when inside of a…

Interesting...let's be even more specific with this, adding the key to the parent check: parent = {{triggerIssue.parent.key}} AND issueType not in (Test, "Test Plan","Test Set","Test Execution", Sub-task) AND statusCategory != Done

Hi @carolina Would you please expand the details in the audit log to show which steps of the rule did execute? The two possible causes for your rule are that the condition was not met or the branch did not find a parent to process. If it is the second one, you can try using a JQL branch instead to get to the parent issue.…

Yes; you could export the rule to JSON and look at the details of the values used.

Hi @Phil Bustin I hypothesize the problem is the rule is using the status id values behind the scenes. Let's try this: * disable the rule * edit the rule to change the transition and condition to check other status values * save/publish the rule * edit the rule to set the values back to what you need * save/publish the…

Hi @Sanjivani Wayal First thing, why would you want to do this? There is often a degree of uncertainty using story points, particularly when trying to use them for forecasting in a scale larger than a single sprint. Using too much precision (e.g., fractional story points) may not help with accuracy. Next, are you asking…

Hi @jalewis -- Welcome to the Atlassian Community! First thing...When you are inside of an iterator like {{#lookupIssues}} {{/}} you do not use the issue. prefix. That would be trying to reference something outside of the lookup, and so may not work as you expect. Please try removing that to see what happens. Next, what is…

Hi @Harry Heathcote The Assign Issue action has a round-robin option which appears to match what you ask: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Assign-issue I have not used this one, and per the documentation the rule is somehow keeping tracking of assignments by this rule to a list…

Hi @Inna S For a question like this, please consider posting images of the complete rule and audit log details showing the execution. Those will provide context for the community to offer suggestions. Thanks! Without knowing the structure of your rule...how you solve this depends on the relationship between the issues: *…

Hi @Nitzan Matalon I suspect the problem with this rule is the branch for this scenario AND testing for sub-tasks of sub-tasks. You do not indicate how many of each type of sub-task (i.e. QA and not QA) exist for a parent, so I would recommend a different approach... Using either the Related Issues condition with JQL, or…

Hi Troy, and welcome to the Atlassian Community! You may be able to do that with the rule conditional logic. However there is no "Send Email Trigger", although there is an action for that, and so... Please post images of your complete rule and the audit log details. Those will provided context for the community to offer…

My mistake as the smart value name is plural. Please try this, ensuring that you use your project name in the JQL: project = yourProjectName AND status != Released AND fixVersion = {{triggerIssue.fixVersions}} If that does not work, please post images of your current rule and the audit log showing the details of the rule…

Lookup Objects returns a list of things, and so first try accessing one item: {{lookObjects.first.Manager.Jira user.accountId}} Or the list of values like this {{#lookObjects}}{{Manager.Jira user.accountId}}{{^last}}, {{/}}{{/}} If that does not work, you may not have the correct smart values. Those are name, spacing, and…

First thing, there is no built-in way to create release notes as you are doing. I suggest investigating if there is a REST API call to do so from a rule. Next for the error you show, your condition on Issues Fixed In Version only works for a version-related trigger. Instead you would need to use a Related Issues condition,…

Perhaps try this to find the issues, and then iterate over them to link to the trigger issue: * trigger: manual * branch: on JQL of... * project = myProjectName AND summary ~ {{triggerIssue.summary.left(7)}} AND key != {{triggerIssue.key}} * action: link to the trigger issue Please add any additional conditions/tests you…

Yes, and...it appears the defect with the changelog for sprints is addressed, so here are a couple of examples, for a rule triggered on a change to the sprint field: before: {{#changelog.sprint}}{{fromString}}{{/}} after: {{#changelog.sprint}}{{toString}}{{/}}

Thanks for that information. What do you mean by "manual actions"? From what you have described, you will need at least two different rules: * Triggered on issue transition to Released, check if all other issues in the release are complete, and then release the version. * Triggered on version released, do what you are…

I checked a couple of different Jira instances and did not see this symptom. Are you the only person seeing this, or are others also seeing it in your instance? What about with different browsers? You appear to be the site admin for a paid-license version of Jira, so I recommend sending this one to the Atlassian Support…

Hi @Emerson It seems you already have an automation rule. For questions like this, please post images of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Thanks! What have you tried thus far to improve your rule to the new needs?…

Hi @Sankalp Chugh -- Welcome to the Atlassian Community! From where are you seeing that view/symptom: * a Jira board * an issue pop-up from a board * an issue display (side panel) from a board * the backlog * the list of automation rules * somewhere else? Knowing that will help the community attempt to reproduce what you…

Hi @Maggie Spitchka Adding to Mikael's answer...When do you want to know this information? For example: * when something is added to an in-progress sprint * when something is removed from an in-progress sprint * when something is added to a future sprint * when something is removed from a future sprint If you want all of…

Hi @Christi Evans Frist thing: I recommend checking if that gadget is providing accurate enough data for your needs, as is. It seems designed to show Lead Time (time from create to completion), and my quick testing seems to show some reporting errors for that. Next, there are no built-in JQL features to remove the weekend…

Hi @javed.faruquee -- Welcome to the Atlassian Community! First thing: I am not currently using Confluence Automation, and I am basing my answer on what I know of Jira Cloud Automation and the documentation. With that disclaimer out of the way... Confluence Automation is supported with the Premium or Enterprise license…

Hi @Chad Jackson Would you please show what is appearing in the log details after you try those writes? Knowing that may help the community come up with suggestions. Thanks! Kind regards, Bill

What is the purpose of that condition, as it seems to be testing a value against itself? And, would you please show the details of your link issue action? The rule shows "success" but that action does not appear in the log for some reason.

Hi @kcarpenter -- Welcome to the Atlassian Community! For a question like this, please post images of your complete rule and the audit log details showing the rule execution. Those may provide context for what is happening, enabling the community to give suggestions. Thanks! And...if the substring is always 7 characters at…

Curious timing you just asked about this again...I just did this calculation in a spreadsheet to build a support ticket on the built-in, Atlassian interpretation of a control chart, possibly having an error. My basic calculation idea was: * identify your start and ending time of day for business hours * use…

Hi @Michael Thompson Agreed, as I am just another customer :^) There are some very old, basic suggestions that have lingered. Often I find a need to build my own, or buy, to fill those gaps. The products do continue to improve over time, yet I do wonder about the decision-making on the product teams. Kind regards, Bill

Thanks @Tanguy Crusson So the flow seems like... * With user management* Site admin (or above) adds/edits user access for JPD, selecting Creator or Contributor level * And then...Within a specific JPD project...* A Creator can add/edit users...up to the level they are configured as a base user (Creator or Contributor) AND…

Yup, I agree. Those insights are meant to be fast and helpful, so showing disparate information no doubt may confuse customers at first glance.