Bill Sheboy Expert

In each location where you branch on sub-tasks and try to transition them, please try this: * branch: on sub-tasks* condition: status not equal to done * condition: status not equal to "to do" * action: transition to "to do"

Thanks for that information. I recommend parsing out the text version of the date/time as you have done and storing that in a created variable. Then try the toDate conversion on that.

Hi @Jerin Geevarghese In your branch of sub-tasks, have you considered adding a condition to check if the issue is (or is not) in a particular status before transitioning to "to do"? For example, you could add a check that the status is not equal to done. Kind regards, Bill

Well done! Please consider marking this question as answered to help others find solutions faster in the future. Thanks!

Hi @Rob Horan Yes, and...There is this page Atlassian was experimenting with for Recently updated Jira KB articles (Cloud), but sadly there is no way to *watch* it yet. My understanding is that they manually updated it rather than auto-magically doing so.…

Hi @Farah I do not believe that is possible with out-of-the-box Jira. Doing so would remove the team's ability to see the symptom that an issue has been in multiple sprints, to consider what is different about the issue to cause carry-over/moves, and to consider improvements to prevent that symptom in the future. Kind…

Hi @Amit Baghel -- Welcome to the Atlassian Community! That feature appears to be in progress, and you may vote for/watch it to see progress: https://jira.atlassian.com/browse/JSWCLOUD-18668 Kind regards, Bill

Greetings all! An FYI to what I am reading this thread: The Atlassian support team told our company (for a prior outage ticket) that "catching up" on scheduled and triggered rules is subject to the severity and specifics of the outage. The expectation is that rules may eventually run (as Aron notes for queued events) or…

Hi @felix.weber There is an open suggestion to add group ownership of rules, which would allow notification on failures to the group: https://codebarrel.atlassian.net/browse/AUT-2009 Kind regards, Bill

Hi @nouran.akram It appears that you are using the marketplace app Automated Release Notes for Jira. Is that correct? If so, you may want to contact their support: https://marketplace.atlassian.com/apps/1215431/automated-release-notes-for-jira?hosting=cloud&tab=support Kind regards, Bill

Hi @Larissa Akemi Would you please clarify what problem you are trying to solve? That may help the community to provide ideas. For example, are you asking: * I want to see issues stuck for a specific window of time. How may I find issues which remained in a status for exactly 3 days, regardless of current status and…

Hi @Kelly Scott When you review your audit log is the rule triggering? If so, please post an image of the log to give the community some context to offer ideas. If your rule is not triggering, the rule isn't seeing the field change. Instead try the generic "issue updated" trigger, and then test for the changelog for a…

I am unclear what that source format is you are getting, and I recommend starting with just the date in Jira Date format, yyyy-mm-dd, and write the source and the parsed values to the log as you confirm it. Once that works, try adding the time information.

The primary status page looks "decorated" in holiday colors: red, green, black, blue, yellow... :^)

Hi @Frederico Vicente -- Welcome to the Atlassian Community! Yes, and...to what Jack notes: you may watch the status of the outage here and subscribe for updates: https://jira-software.status.atlassian.com/ Kind regards, Bill

Hi @Seth Hettich -- Welcome to the Atlassian Community! Yes, and...to what Fabian suggests: Once you get your date into a string/text format, try using toDate to convert it. Kind regards, Bill

Hi @Daniel -- Welcome to the Atlassian Community! If I am understanding your use case correctly... First thing, nextgen (now called Team-Managed Projects) cannot have multiple boards yet. That means you are talking about linking/updating issues in different projects and that requires a global / multi-project rule. Correct?…

Hi @Sofia Quintero Yes, and to what Trudy suggests: The Lookup Issues action now supports most fields, and so you may be able to sum up the values with a JQL statement and Lookup Issues for the types you want without a work-around to use the Story Points to hold the values.. Kind regards, Bill

Hi @Alex Koxaras -Relational- In case you did not see it, Lookup Issues now supports most of the fields. Please consider updating your article as that reduces the need to use Story Points as a proxy field to roll up other fields. https://community.atlassian.com/t5/Automation-articles/New-lookup-issues-fields/ba-p/1873978…

Hi @Collin Shawler Short answer: I do not believe this can be handled yet. Longer answer: There are a few open defects on this symptom, such as these two examples: * https://jira.atlassian.com/browse/JIRAAUTOSERVER-306 * https://codebarrel.atlassian.net/browse/AUT-2200 As your use case is slightly different, and you are…

Hi @Preston Hicks -- Welcome to the Atlassian Community! For a query like that, try splitting it apart and rebuilding it incrementally. I suspect you have an order of precedence problem with your AND and OR expressions. * List all of the things true for everything you expect first* something AND somethingElse AND…

What is the error you are seeing in the audit log? Would you please post an image of the log showing the error and your complete rule? Thanks! One challenge with your solution approach is that you are trying to represent three conditions/pieces of information with one custom field: * custom field is empty: no timeout to…

Hi @Elizabeth Cromwell -- Welcome to the Atlassian Community! You could use some advanced JQL functions to do this. For example to find issues due after the end of today and before the end of the week it would be: project = MyProjectName AND due > endOfDay() AND due < endOfWeek() Kind regards, Bill

Hi @Hadas Hamerovv One approach to do this is not to set a default value. Instead use a transition-trigged rule which checks if the timeout field is empty, and then set it to {{now.plusHours(12)}} as shown here: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Example.6 If instead the…

Hi @Caleb Ciampaglia You may use {{initiator.displayName}} to see who did the action which triggered the rule. Kind regards, Bill

Hi, Joost. You are very close to solving this! The key here is how do you connect your features and epics: custom field, parent, link etc.? Then write a JQL statement that selects all the siblings. For an example patterned from your rule image and assuming use of Parent Link: * trigger: story points change * condition:…

Hi @jbedar To be honest, I am not using business projects and cannot try what you asked. Is this suggestion the feature you are asking about? https://jira.atlassian.com/browse/JWMCLOUD-6 Kind regards, Bill

Hi @Joost Klykens To do this with automation, I recommend using a JQL statement to gather the epics with the Lookup Issues action. You may then get the sum with: {{lookupIssues.Story points.sum|0}} Kind regards, Bill

Hi @Apryl Harris Using the REST API, perhaps you could get all boards, filtered by the project, and compare the id values. The lowest id is probably the first one for the project, and then check the type in the results.…

Hi @Paul Marachlian This appears to be a known issue for some custom field types. You may vote for/watch this defect to see progress on fixing it: https://jira.atlassian.com/browse/JRACLOUD-77607 Kind regards, Bill