Bill Sheboy Expert

Hi @Marc Blascak When adding the scheduled trigger to your rule, did you note this link to documentation on CRON expressions: https://support.atlassian.com/jira-software-cloud/docs/construct-cron-expressions-for-a-filter-subscription/ Please take a look to see how that helps. Thanks! Kind regards, Bill

Hi @Adam Taylor What you describe seems like a very, narrow use case to me. It might be possible and I recommend breaking it down into pieces to build-up slowly to see if you can do it. For example, what do you mean by "a certain label has been used more that 20 times in the past 30/60 days" * used more than 20 times on a…

Hi @Rick Crow When do you create the sub-tasks, with the task creation or at some later timeframe? And, have you confirmed the names of the smart values match your custom fields? (Sometimes they are different and so the custom field ID is needed.) To find those, try the steps in this…

Hi @Danielle David -- Welcome to the Atlassian Community! Yes, and...to what Alex suggests: I do not believe there is much available yet for management of automation rules. And these things are "code" in an project/instance-scale solution without source control or a release pipeline. To me that means I should treat them as…

Hi @Deepak Thomas I am not with the Atlassian team, but I wanted to suggest this article to give you some ideas/steps to try: https://support.atlassian.com/bitbucket-cloud/docs/reduce-repository-size/ Kind regards, Bill

Hi @SMK -- Welcome to the Atlassian Community! Would you please clarify what you are asking, as that will help the community to offer ideas? Thanks! For example: do you mean "Jira prioritization" or prioritization, in general: * Jira: You could use the priority field, or whatever other field(s) you decide to help…

Hi @Jamie Eliya You may want to look at this article describing the new conditional processing for smart value lists. Seems like that could help with what you asked. https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 Kind regards, Bill

After searching a bit, I could not find out if that one is deprecated. Maybe try to post the same question in the developer community: https://community.developer.atlassian.com/ And, ask your site admin to submit a support ticket if you are on a paid license: https://support.atlassian.com/contact/#/ Once you hear back from…

Glad to try to help!

Hi @Chris Green I do not know if that method is deprecated, but since GDPR went into effect you cannot call such methods with the user name any longer. Please try with accountId with the appropriate value to see if that helps. Kind regards, Bill

Yes, you may add the parent info to the description as I did in my example. To add that same info in another field, just edit it as well.

Thanks for the additional information, Aaron. I am a bit unclear on what you mean by "description footer". To add the information you note as text to the description, a simple example rule is below, assuming the parent is an Epic and this is a company-managed project: * trigger: unclear what you want here, but it needs an…

Hi @Michele Bazzani -- Welcome to the Atlassian Community! I believe drag-n-drop ordering only works when the board filter uses ORDER BY Rank. You could order by another field, but then lose all drag-n-drop ordering. Are you using a company-managed or a team-managed project? And, you note 100s of issues apparently on the…

Hi @Reid Bourgeois Have you tried using the attribute name "id" instead of "accountId", like in the documentation: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/#Advancedfieldediting-JSON--Requestparticipants Kind regards, Bill

Hi @A A Ron Geister _Trundl_ -- Welcome to the Atlassian Community! You could add the key and creation date of any linked issues to the end of the description field with automation. However, what problem are you trying to solve by doing this? Some notes before trying this rule: * This could get "noisy" when there are…

Hi @[deleted] Agreed: the string of list/text functions to solve this can be a mess, both to implement and to test. One work-around others have tried for the create variable/branch limitation is entity properties or a custom field. You could write to the property (or field) and then use a re-fetch action to access it…

Hi @Christine P. Dela Rosa My favorite/least favorite is "Dear Work Therapist Q&A": * like: there are some ideas which help me think about my teams' interactions, and offer community perspectives demonstrating vulnerability and openness to change * dislike: some of the ideas seem presented as click-bait or for authors to…

Hi @Sue Hannan What do you mean by "copy"? What is the source of the value? If you are trying to copy from another field, I believe you need to use the advanced edit features: https://support.atlassian.com/jira-software-cloud/docs/advanced-field-editing-json/#Advancedfieldediting-JSON--Timetrackingandloggingwork Kind…

Thanks, that helps quite a bit! I am on the Standard license and so do not have Initiatives. That being noted... This suggestion says the advanced roadmap/portfolio hierarchy is not supported by automation yet: https://jira.atlassian.com/browse/JRACLOUD-74105 A possible work-around might be: If Initiatives linked to Epics…

Hi @Sam Harding Given your examples use {{issue}}, {{lookupIssues}}, and {{issues}} it appears this change works with both Cloud and Server/Data Center. Is that correct? Thanks, and kind regards, Bill

Hmm...I tried this and it worked for me to copy the links from the Epic to any child issues of the epic.

Thanks, Brett. Are you certain that is the correct log, as it does not match the rule image you posted? For example, there is no indication that the condition did/did not match.

Brett, please try to keep to one thread as that will help others in the future know if there are multiple answers to a question. Thanks! What type of project is this: company-managed or team-managed? And, would you please post an image of you audit log showing a case when you expect the rule to trigger? Remember to expand…

Hi @Brett Fitzpatrick Does the audit log show the rule triggering? And, two suggestions to help: * after the trigger add a condition to confirm the issue type is Epic * in your edit issue, change to use Copy From Trigger Issue, rather than current issue. Kind regards, Bill

Hi @Anish Taneja -- Welcome to the Atlassian Community! You are leaving some details out of your question, so if I assume that you want: * a scheduled rule with some JQL criteria * want to send one email with issues per relevant assignee The answers I can think of depend upon if you are using Jira Cloud or Server/Data…

Hi @dnevarez -- Welcome to the Atlassian Community! Please start with the top navigation bar...Filters > Advanced Issue Search Kind regards, Bill

Hi, Ernesto. An example automation rule to do this would be: * trigger: issue commented * action: edit custom field with the last comment's body: {{issue.comment.last.body}} Please look here to see other data available from the comments:…

Thanks for that information. You may want to investigate using the built-in velocity and version reports, and perhaps the dashboard gadgets with filters: https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/ If those do not meet your needs, I suggest making a short list of what you want to see…

Hi, Sam. Very interesting! Do you note the differences between our rules which do exactly the same thing? You apparently set the date criteria first while I did the date set first. Looks like a bug to me as the triggers are different *and* the same. Perhaps try to do what I did by creating a new rule, selecting the date…

Hi @[deleted] If you review the comments for this post, you will see this technique only works when the branch has one-and-only-one issue, apparently determined at rule creation time. Otherwise (according to the help documentation) the branch loop runs asynchronously, each variable inside is new/disposed of, and there is…