Bill Sheboy Expert

Hi @Jim Weaver -- Welcome to the Atlassian Community! Are you asking about the impacts to the team or to Jira behavior / reporting for terminating the sprint early? For the team, I recommend discussing with the team and their coach / scrum master how they handle such occurrences. Perhaps also review the out-of-the-box…

Hi @vincenzo.spatafora I do not believe there is anything built-in capable of sending the page as a PDF export using an automation rule. Please check the Atlassian Marketplace for an addon to do this type of reporting. Kind regards, Bill

Hi @Roman Malynovskyi -- Welcome to the Atlassian Community! What type of project is this: company-managed or team-managed? You may find that information at the bottom, left side of the page expanding area. And when you note you "duplicated the same fields to a Child issue", did you add the existing fields to the subtask…

Hi @Alexandra Peia Please provide images of your advanced branch details and of the audit log details showing the rule execution. Those will provide context to help explain the symptom. Also, what was the specific change you made to the rule, after which it stopped working as expected? Kind regards, Bill

Hi @Robin_Janott There are two ways to accomplish the conditional summation: #1) Use the Lookup Issues action with JQL to gather the subtasks meeting your criteria, and then sum on the field for the issues found: {{lookupIssues.customfield_10241.sum}}…

I do not understand what you are describing. I recommend meeting with your Jira Site Admin to discuss the configuration and ask for their help. Two boards are not "linked with a filter". A single board has one filter, and that impacts which issues are displayed. A filter expression could be used for zero-to-many boards.…

Hi @Harshad Prajapati -- Welcome to the Atlassian Community! The condition syntax with else handling looks like this, without the leading pound sign: {{if(some condition, "True value", "False Value")}} And so that cannot use the nested, long format math expression inside of it. To do this with an inline math expression,…

Hi @[deleted] Are both of those issues in your current sprint for the board? Do you have any filters selected on the board which prevent displaying both issues? Kind regards, Bill

Hi @Christoph Keßler -- Welcome to the Atlassian Community! Theoretically...an automation rule could call the Confluence REST API with the Send Web Request action to get the page content, and then parse the HTML in the table to get the value. An example call could be this one: your Jira URL/wiki/rest/api/content/your…

Hi @Nadege When was the last time the rule was modified? Could the next-start have been modified? Next, there was a performance issue reported yesterday, although that seems workflow related: https://jira-software.status.atlassian.com/ Regarding when scheduled rules trigger, my understanding from community posts by…

Hi @Oza Parth -- Welcome to the Atlassian Community! For this type of reporting, I recommend checking the Atlassian Marketplace for apps to report or provide dashboard gadgets to do this: https://marketplace.atlassian.com/ Kind regards, Bill

Hi @Aline Veyradier It can appear for all license levels...if it has not been disabled. For Cloud, it may take a bit to reach all sites. Please look here to learn more about the feature and how it may have been disabled for a user /…

What is not working as you expected with your rule? Please post an image of the audit log details showing the rule execution. That will provide context for what you describe as not working as expected.

Thanks for clarifying, and that is a known limitation in many places: * parent summary on board grouping, as you show * selection of parent in issue edit * the opposite problem for display of children, such as sub-tasks * etc. I did not find any open suggestions to modify that behavior, so you could add one or send…

As I understand it, People fields are only used by team-managed projects, including software, Jira Product Discovery (JPD), and Jira Work Management (JWM) types. The missing information such as email address is a limitation of the People field type. That appears to be one of the reasons Atlassian added the ability to share…

Hi @Vijay Kumar -- Welcome to the Atlassian Community! The sprint's endDate attribute is not available with built-in JQL, and so may not be used in a query. If your sprints are occurring on a consistent cadence you could try a Scheduled Trigger rule, selecting the starting point and frequency to align with your sprint's…

Hi @Damian Parker Short answer: it seems cover images can only be set by some code in the UX; they cannot be set with automation rules or the REST API. I experimented a bit and this is not a permissions issue (for the rule) or a problem with the attachment not copying correctly. It seems the board's user experience (UX)…

Hi @[deleted] -- Welcome to the Atlassian Community! Short answer: maybe. I recommend waiting for one of the community champions / administrators to respond...or ping one of them by name from the Welcome or Kudos groups for their input. The last time I did what you describe was a couple of years ago. At that time, my level…

The expression you show will work if there is a list of issues and not a single one. Please try this one which only iterates over the sprint values for a single issue: {{#issue.sprint}}{{#if(equals(state,"active"))}}{{name}}{{/}}{{/}}

Hi @Gina -- Welcome to the Atlassian Community! You describe this: "...an issue without an end date is added to the release". What do you want to do if the issue already has a Due Date (i.e., end date) value? Next, the Fix Versions field in issues is a list of values. The smart value expression you show will: * for each…

Hi @George Davitaya Would you please clarify what you are trying to accomplish? For example, if you want to create an Epic and then add child issues to it, the rule may branch to the most recently created issue to help set the parent: * trigger: some trigger * action: create issue (an Epic) * branch: to the most recently…

Hi @Nguyen Thanh Tien Each issue would need to track when the reminder was sent, such as with a date / time, custom field. That field could be checked with JQL in the rule trigger to select the correct issues. Your first rule, with the first notification, would initially set the custom field for later use. Kind regards,…

Hi @Stephan Blonk -- Welcome to the Atlassian Community! Would you please post an image of what you are observing? I believe the Summary field is limited to 255 characters, and when I tried with a few different board and project types, the full text was displayed. Kind regards, Bill

Hi @Sanyal_ Kunal No, the built-in reporting uses the current estimation value. It does not detect / report changes over time as you describe. If you wanted to see the prior history you could investigate marketplace addons / apps which add such reporting or dashboard gadgets. Their reporting is likely independent of the…

Hi @Aurélie Pilette Please post an image of the audit log details showing your rule execution. That will provide more context. For the issue your rule is trying to update, does the Sprint field already have the value selected? The smart value expression you show will only provide the current sprint if it was already…

The if / else condition cannot be used inside of a branch on Parent. And so the way you wrote your rule will stop as soon as it fails a condition. That can be inverted, with the branch inside of the conditions... The rule structure I was suggesting is more like this, using create variable, math expressions, and list…

I am glad to learn that helped, and... Your rule uses the Issue Created trigger. That one can fire so quickly that some data may not yet be available to the rule. This may cause unexpected behavior (e.g., incorrect condition results) or errors. To solve this I recommend always adding the Re-fetch Issue action immediately…

Thanks for that information, and I still believe this can be done in one rule (if the intent is to manually trigger it and create all the issues at once. If you save the key after each issue is created, and then use branch on JQL, this will work. For example: * trigger: manual * if / else condition* ... conditions to…

Thanks for that information. You could iterate over the comments, as I noted earlier, and use smart value, list filtering so only the comments for the last day are included: https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588

Hi @Hannah McKenzie How may customers on a free license level disable this feature for their entire site when they cannot submit a support ticket to Atlassian? I noticed community posts about this potential need as soon as the experimental version of the smart reply comments started appearing a few weeks ago. Kind regards,…