Bill Sheboy Expert

Hi @技術處-數據資訊部-維運組騰輝 That appears to be a known, new defect, which you may watch / vote for here: https://jira.atlassian.com/browse/JRACLOUD-84882 Kind regards, Bill

Hi @Perry Wong If the different teams are performing different work specifics to deliver value, why would they use the same Jira issue / work item to manage their work? That approach may not align well with some of the built-in reporting for Jira Cloud. An alternative approach for what you describe is to have a "parent"…

Hi @Rilwan Ahmed and @Lea S For this scenario, the rule needs to use the if / else condition structure rather than individual conditions. Otherwise the rule will halt on the first failed condition. Another alternative is to use a Lookup Table, where the keys are the assignee's displayName and the values are the email…

Thanks for that information, and it appears the nested list-within-list is causing the problem: {{issues}} is a list and the {{sprint}} attribute is a list. As your trigger uses JQL to find the issues in the openSprints(), let's limit your condition to just check the first one:…

Hi @Julie Shepard -- Welcome to the Atlassian Community! There is an open incident related to this symptom, which you may follow here: https://jira-software.status.atlassian.com/incidents/wcs79hfp1npb If your rule continues to have problems after that one is resolved, I recommend working with your Jira Site Admin to submit…

Hi @VAlesbury -- Welcome to the Atlassian Community! As this is an older thread, I recommend creating a new question, and perhaps linking back to this one. That will ensure the maximum number of people see it to offer suggestions. Thanks! When you post your new question, please include: * what problem are you trying to…

Thanks for that information, @Vyshnavi S Is your question resolved / answered for this one?

It would be a separate rule: one rule with the Issue Created trigger to send the first message, and the second one with the Scheduled Trigger for soon-to-expire SLAs.

Hi @Brian Debler As @Laurie Sciutti was noting, perhaps you are blending some Jira terminology, and the Resolution field would be better. * Issues have a Workflow (i.e., a process shown as a state diagram), compose of a series of Status values * Each Status has a Status Category value, with one of the following: To Do, In…

The image you show of the advanced compare is trying to compare a date value to 4. The smart value I provided was what to use with the diff() function, not the entire expression. Please update your condition to: * first value: {{now.diff(issues.first.sprint.endDate.max).days}} * condition: equals * second value: 4 Then…

Hi @viraj I believe your second rule to check the SLA could use a Scheduled Trigger with JQL, checking remaining() for the issues: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#remaining-- Kind regards, Bill

When you use a smart value in the JQL, it is dynamically generated when the rule runs using the smart value. And so the only way to confirm it works is to run the rule.

In that case, please test your rule and let us know if it is working as expected.

When inside of an iterator, such as {{#issues}}...{{/}} the issue prefix is not used; the scope is the iterator. For example, this would list the issues and their original estimates: {{#issues}} * {{key}} -- {{timetracking.orginalEstimate}} {{/}} This would sum the values, without the iterator:…

Hi @관리자 Some of the things you describe could be done with the built-in dashboards, timeline view, or advanced roadmaps. Some of the other things could not be done with built-in features, and would require external reporting or marketplace apps...which you describe not wanting to use. I recommend creating drafts of the…

Hi @Brian Taylor I suspect that depends upon the marketplace app you are using to connect Jira and Slack. Please check with your Jira Site Admin and then review the marketplace information to learn which fields can be used / configured to create Jira issues from Slack.…

Hi @Gabriel Vargas -- Welcome to the Atlassian Community! For automation rule questions, it helps to show your complete rule in a single image, and an image of the audit log details showing the rule execution. Those will provide context for the community to help better. From what you show... To change issues with the edit…

Hi @Santhosh Velmurugan -- Welcome to the Atlassian Community! Adding to Trudy's suggestion: Smart values are name, spacing, and case-sensitive. When an incorrect one is used, that returns null. To identify the correct smart value (or custom field id) for your field, please use this how-to…

Hi @Vijay Kumar -- Welcome to the Atlassian Community! Do you have the bulk-handling option selected for your rule's trigger? https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html If not, your rule will, iterate over multiple issues (potentially sending multiple emails) And, if the…

Hi @john.monteith Well done solving your own question! FYI this how-to article may help in the future to see the supported smart values, and their structure, which is available to rules: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Kind regards, Bill

Hi @Vyshnavi S First, what have you tried to solve this need? If you have an automation rule and it is not working as expected, please post images of the complete rule, the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer better…

First, I am just another Jira user and have no knowledge of their progress resolving issues. I have seen a couple of other posts recently about this symptom, and I wondered if the Atlassian team's in-progress work is creating other symptoms. I recommend contacting the Atlassian Support team to learn if that is the case.

Hi @Christian Short answer: maybe. Depending on the type of checkbox field (i.e., built-in type or marketplace addon), the information about changes to the field may be in the issue history. If so, one could write code to read the issue history to examine the changes over time, and calculate the duration. Also, if changes…

I believe this depends upon what "action" you are trying to accomplish. For example, one could provide a direct link to an issue attachment, and that would trigger a download of the attachment (for licensed Jira users). What problem are you trying to solve? That is, "why do this?" Knowing that may help the community to…

Correct: I tested and this appears not to work for linked, team-managed project (TMP) ideas. I recommend submitting a defect (or feedback) for it to the Atlassian team: GIVEN a JPD idea exists AND it has linked delivery issues in a team-managed project AND the delivery issues have values for the "Story point estimate"…

Understood, and...I wondered if their rolling out "fix" is causing side effects. I recommend pinging the support team.

Hi @Marcia Booth There is an in-progress defect related to the symptom you describe: https://jira.atlassian.com/browse/JRACLOUD-84725 If that does not resolve the problem, I recommend working with your Jira Site Admin to contact Atlassian Support: https://support.atlassian.com/contact/#/ Kind regards, Bill

Hi @Doug Winenger There is an in-progress defect related to the symptom you describe: https://jira.atlassian.com/browse/JRACLOUD-84725 If that does not resolve the problem, I recommend working with your Jira Site Admin to contact Atlassian Support: https://support.atlassian.com/contact/#/ Kind regards, Bill

Hi @Annie Kearns Is that planning poker feature from an Atlassian Marketplace addon / app, rather than a built-in feature? If so, perhaps check the vendor's marketplace page to contact their support team: https://marketplace.atlassian.com/ Kind regards, Bill

Please try this as your custom filter: statusCategory != Done OR ( statusCategory = Done AND statusCategoryChangedDate >= -3d )