Bill Sheboy Expert

I believe the basic, REST API endpoint for issue edit may only update the Sprint field and does not clear the history. You could experiment with the newer bulk-edit endpoint to see if will clear the history, although I hypothesize it will not: the primary idea of issue history is it is immutable, and if the endpoints could…

Thanks for that information, @Travis Hill As this is a reporting need, have you considered investigating Atlassian marketplace apps / dashboard gadgets which could present a saved filter as a grid with selectable columns? That may allow showing parents with child issues below each for that reporting field, and allow…

Backing up a bit: what problem are you trying to solve by doing this? That is, "why do this?" Knowing that may help reveal other solution approaches. Until we know that...I will try to answer each part of your post, so please let me know if I miss something... I need to do this for several hundred tickets at a time When a…

Hi @Mark Taranenko -- Welcome to the Atlassian Community! JQL is not an SQL, and thus it does not have features to return a specific number of issues. There may be marketplace addons to JQL which provide this capability, although I have not used any of them. For the scenario you describe, I know three ways to get a…

Hi @Travis Hill First thing, what version of Jira are you using: Cloud, Server, or Data Center? That impacts how to solve this for the different versions of automation features. For example, with Jira Cloud, the Lookup Issues action could be used to access the custom field and gather the…

First, I will try to answer your question, and then try to clarify a bit... The statusCategoryChangeDate only gets updated when the Status Category changes, and not necessarily for each change of the Status. Thus when you have multiple Status values with a Category value of "In Progress", that date may not be what you…

Hi @Joshua Smith Following that how-to article helps to send one-email-per-assignee with their respective issues: https://confluence.atlassian.com/jirakb/automation-to-send-email-only-once-per-assignee-1310985609.html Please note that the rule uses the advanced branch over Assignees and not issues. As a result, the Comment…

Hi @Don Utley Would you please show an image of your rule's Edit Issue Fields action and of the audit log details showing the rule execution? Until we see those... I hypothesize you are trying to use that expression you show in the advanced edit with JSON, but it is neither valid JSON nor a valid conditional…

Hi @Joe_Noel I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @Itsel Vazquez I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @Surya Pindiprole I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @Rob Terakedis For Jira Work Management (JWM) projects, I believe that type of Category may only be added when on the List view. On which view are you trying to add a Category? Perhaps add a screen image for context also. Thanks! Kind regards, Bill

Hi @Brian Gauthier I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @Mythili -- Welcome to the Atlassian Community! I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @Sushil Ranjan I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @Christine -- Welcome to the Atlassian Community! I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @Christophe Ventura I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @A.M.E.C I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Hi @margat I am following up to learn if you are still working on this one or if the suggestions resolved it. If resolved, please mark this question as "answered" to help others with similar needs find solutions faster. Thanks! Kind regards, Bill

Thanks for the screen images, and...is the Stakeholders field a global, user-picker field or a People field? If it is a People field, the email address is not available to automation rules yet (as it is not available to the REST API endpoint which rules use): https://jira.atlassian.com/browse/AUTO-519 You may test that by…

Hi @jodywhite Short answer: from the issue history. The changes to issues are recorded by the date / time they happen. When the issue is added to a Sprint, the specific changes and when they happened are added to the history. The Sprint report reviews the issues which are (or were) in the Sprint and parses the history to…

Hi @Susan Merola The Due Date field is a "date type" and Labels are text. The date value must be formatted to be used as a label, as described here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- For example, you could use this to get just the year value as text:…

Hi @Jarrod Reimann For a question like this, context is helpful. Please post images of your complete automation rule and the audit log details showing the rule execution. Those will help the community offer better suggestions. Thanks! Kind regards, Bill

Great; thanks for clarifying! Other than "oops" situations, the rule you show will handle issues added to an Active Sprint or a Future Sprint. For safety, I recommend adding one more condition after the trigger to check the status is not "Done" (or whatever you use for "completed"). To clean-up / fix completed issues'…

Thanks for confirming the scenario! First thing: unless someone sets the Status to "Done" when the issue is created, one rule will work for this. A condition may be added to prevent problem. The key is you to update the created issue from its parent using a lookup rather than a branch as the source, and so let's try this:…

Thanks, I just learned something new: the user smart value now provides "groups". Let's modify the approach I described earlier to use that information... Testing indicates the groups smart value appears to be one of the dynamic smart values, which is found just-in-time when it is used. And so to query it, the values must…

That depends upon what you want to know... A simple JQL to find issues not-yet-done and possibly removed from a Sprint is this: project = myProject AND Sprint IS NOT EMPTY AND Sprint NOT IN openSprints() AND statusCategory != Done ORDER BY Key ASC And if the Sprint field is included in the results, it shows which completed…

That is similar to what I described, and often needs at least the first and third rules I described to accurately detect issues removed from the sprint. Please note well: if people can delete issues from Jira, those will not be found. In general, I recommend removing the delete-issue permission from everyone except Jira…

That result implies customfield_16609 is a number field, and not a text field. Are you certain you tried this expression using it as a number: {{issue.customfield_14329.minusDays(issue.customfield_16609)}} Are you certain customfield_14329 is a date (or date / time) picker field? If not, let's try this to convert from a…

First, your rule steps are out of order: the condition should be after the table is created! Next, there is a typo in your condition you highlighted: there is an "a" before the issue smart value. Finally, I believe you want the condition to be "not equals" empty, thus the rule continues to run if a value is found with the…