Bill Sheboy Expert

Hi @Ryan Maddison -- Welcome to the Atlassian Community! There are several ways to do this, starting by using the CHANGED operator for JQL with the DURING or AFTER modifiers for the date / date range: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED With your JQL expression ready, you could: *…

Hi @Andreas Safar First thing, I have not tried what you ask, although I believe it would be possible in a rule... The {{issue.watchers}} smart value as an {{active}} attribute for each watcher. And so you could check for a value of false and remove…

Hi @c.ermeier Yes, that is possible with an automation rule. When do you want this to happen and where do you want to place the sum? The "when" will determine which rule trigger to use, and the "where" will determine your specific rule actions, such as updating a field in the parent epic, sending an email, etc. I recommend…

Hi @Rebekah Myers For your scenario, there are several things to consider to get to a solution: * Issues can carry-over between sprints, and so the sprint field can have multiple values * Typically time tracking estimates are in working hours, and not calendar hours. If you are instead using calendar hours, please clarify…

Thanks for clarifying, and the answer is you will need a global or multiple-project scope rule to do this. Your Jira admin can help create such a rule in the global automation view / area, using their elevated permissions. Project scope rules can create or clone issues into other projects. But they cannot access them…

My apologies as I should have actually tested that: it appears the field can be added but it does not display. Here is a suggestion to fix that: https://jira.atlassian.com/browse/JRACLOUD-79341 A work-around would be: * add a custom field which can be added to the issue view * add automation rules, triggered on time…

Hi @Bob Hannau Last Viewed appears to be any individual viewing of the issue: separate browser tab, selection pop-up, or selection sidebar viewing. https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Last-viewed Although that value does not appear to have anything to do with what you are measuring for…

Hi @Brock Jolet Have any of the issues been in multiple sprints, such as carry-over from prior sprints? If so, please consider {{lookupIssues.sprint.distinct}} is... * grabbing the sprint from each issue in the result set * where those could be lists of values for an issue * and then performing distinct on the lists of…

Hi @Jason Rittenhouse and @Summer Hogan It appears that idea was suggested a while ago and closed as "won't do": https://jira.atlassian.com/browse/JRACLOUD-30199 Perhaps review that one and then consider adding more / different benefits if you add a new suggestion. Thanks! Kind regards, Bill

Yes, and...Some teams exclude issues with an Abandoned field set using the board filter, as that will immediately remove them from the board and reporting, even though they finish with the sprint. That is the Jira Cloud behavior; I do not know if that is the same for Jira Data Center.

Hi @Brad H -- Welcome to the Atlassian Community! By default, the actions of one rule cannot trigger another. This is to prevent errors, such as run-away looping. Your first rule performs actions to copy fields from the Epic to the child Stories, but the second rule does not start / trigger because that is option is…

Greg, we do update the status to "done", ensuring the issues complete in the sprint and do not carry-over. Some teams use a checkbox field to indicate "Abandoned", adding a comment to describe why-abandoned, and this helps with reporting in the future.

I reproduced what you are observing, although I do not specifically recall the earlier behavior to confirm what changed...I think you are right that something is different. * when an issue is manually cloned within a project, the clone links are added * when an issue is cloned using automation, to the same or different…

Please see my above comments, as this service function is experimental and has a limit on the number of records returned.

I am glad to learn you solved it :^)

Awesome; I am glad to learn that helped! If this solves the remaining questions, please consider marking this one "answered" as that will help others with similar needs find solutions faster. Thanks!

Hi @Stephen Kaiser -- Welcome to the Atlassian Community! Until it doesn't work... :^) Anything in automation rules doing multiple things / looping (e.g. branches which could be on multiple things) appears to run in parallel and asynchronously. There is no defined processing order and no guarantee of when such branches…

Yes, it will...and perhaps that is okay for how a team works. What Atlassian calls "commitment" for sprints remains the same but the burn charts and other reporting will show the change. For myself and teams I have helped, we do nothing for cancelled items. We chalk it up to learning and discuss it in the retrospective:…

Hi @Greg Mueller Yes, and...to Trudy's ideas, and as an answer to your question, "what do people typically do with cancelled items": It depends upon the team and org. Let's say a team has a Cancelled status, and they want those items not to be reported upon. The board filter could be updated to exclude Cancelled status,…

Hi @Mark J I am unclear what problem this scenario would be solving. Perhaps if you clarify that it will help the community to offer better suggestions. Thanks! Until we know that... From what you describe, I expect you will need multiple rules, and need to invert your thinking about the triggers, such as "when the issues…

Hi @Greg Mueller My understanding is the only way to do that is to re-open the sprint, finish the item during that now opened timeframe, and then complete the sprint again. This will have consequences as the sprint end date / time will change. To learn more, please look…

Hi @Cesar -- Welcome to the Atlassian Community! The businessDays unit of measure for differences is whole numbers only. And, I believe it uses defined values for the working days and hours: it does not use any configuration settings for the…

Hi @[deleted] When using automation rules to access linked issues, such as the parent of an issue, all of that parent's fields are not immediately available. There is some subset of the fields directly available for the parent, such as key, summary, status, etc. but not all custom fields. The reason is one of scale and…

Hi @Dd Without seeing the specifics of your automation rule, I believe what you describe is possible using several different possible text functions: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ Perhaps review those ones for extracting substrings or using the match() function, and try…

Hi @MARCO EBERHARD Adding to John's answer: Without seeing the exact smart value expressions you are using for the branch and the variables, and your entire rule, it will be difficult to diagnose what you describe. Providing this information is essential when asking for help with automation rules. If you are only trying to…

Hi @Rimsha Khan -- Welcome to the Atlassian Community! FYI there are several posts in the community for this specific scenario, so it is often helpful to search around for those; some may exactly match what you need. What you tried with dot-notation on the status / completed state will not work as "completed" is not a…

Hi @Raphi Levine When writing a rule and testing the JQL with the "validate" link, it uses the permissions of the person editing the rule. But when the rule triggers, it uses the permissions of the rule actor. Have you checked if the rule actor has been changed from the default of Automation for Jira? Kind regards, Bill

Hi @Alex Hall To make such multiple-project (or global) scope rules work as expected, please try using conditions to limit the processing. For example, in your scenario: * when issue created in Project A, * look for matching issue in Project B, and when found* close the issue in Project A * add a comment to the issue in…

Hi @Bikram Agarwal There was (and may still be) an old Greenhopper REST API function for the sprint report, and no doubt that is sunsetting. I have not found a new one to replace that. Some other options are: * There may be marketplace addons to do this same type of report for sending to those without Jira access. * You…

Hi @Pjotrs Obuhovs -- Welcome to the Atlassian Community! Do you mean you want the active (or future) sprint stored in the "Actual Sprint" field, ignoring any closed ones? If so, you may try filtering on the sprint state, and then return just the sprint id value. For example:…