Bill Sheboy Expert

Would you please post an image of your advanced compare condition? That may help uncover what is happening. Thanks!

Hi @Nofar Ben Kereth Have you tried using the advanced compare condition and check the field using the smart value: {{issue.Severity Timestamp}} Best regards, Bill

Hi @Derek Small Sub-tasks are children of a task or story. Tasks are at the same level as story, so you cannot move a task under a story. If you have a sub-task that you want convert to a task, you can: * Change your board view to make sub-tasks visible with Group By * Select the sub-task you want to convert * Under the…

Hi @Sigrid Schoepel Regarding the first rule you note and the timing issues, there are definitely race-track conditions in the automation rules due to the asychronous processing, particularly after the create issue trigger. One work-around I use is to put a Re-fetch action immediately after the trigger. It does slow the…

Depending on your project backlog size, you could do a work-around and export to a spreadsheet to perform the query also. __Bill

Hi @Giorgi Nadareishvili -- Welcome to the Atlassian Community! In addition to what @Walter Buggenhout noted, there is a suggestion to add Quick Filters to NextGen, which would allow you to configure filtering. You may review and vote for the suggestion here: https://jira.atlassian.com/browse/JSWCLOUD-17446 Best regards,…

Hi @Surbhi Gupta -- Welcome to the Atlassian Community! I believe you would need to get the issues for the epic, and then determine the progress you have defined yourself. The reason is that different teams could define "% complete" differently, based upon the status and other fields of the issues. The documentation for…

Hi @Elsa Sousa There appears to be a pending fix for this defect, which you may view and vote for here: https://jira.atlassian.com/browse/JRACLOUD-74809 Best regards, Bill

I have not used any of the marketplace addons for this, so please consider doing a search to look at the products: https://marketplace.atlassian.com/search?hosting=cloud One other approach (outside of Jira) would be to use the Excel add-on from Atlassian, which is free I believe. You could then pull data from a filter and…

Greetings, community! Quick tip: created variables do not appear to work as inputs to functions, such as: {{issue.description.replace(myVariable, "my new text")}} What happens is the variable evaluates to null and collapses the function, even when you add null handling. Maybe there is something up with the typing of the…

Hi @Michele D_Adamo You can remove a component using automation with custom fields and the list, string, advanced JSON edit, and create variable functions. It is a bit messy, so if you want the details of how to try this, please let me know. Summary of how this works: concatenate the component values into Json, remove the…

Hi @Samuel Smiles P There is no out-of-the-box gadget to do that. There may be one in the marketplace to purchase. As a work-around, and depending upon how many projects you have, what about creating 2-dimensional gadget for each project on the dashboard? You can still see them all at a glance on one board, even though the…

Hi @Vugar Jafarov There is no way to do this with out-of-the-box Jira Cloud. Two work-arounds would be: * Look in the marketplace to see if there is an add-on which has better visibility to logged activity * Use a webhook to broadcast site changes, and then use a log file parser tool, external to Jira, to see such activity…

Hi @Ryan An approach seems related to what you are trying to improve. For example, * Are you trying to reduce the number of automation calls per issue creation? * How soon after issue creation do you need the additional tasks/sub-tasks? * Etc. Unfortunately, rules are limited to 64 components (I believe) so no ginormous…

Thanks for clarifying! I do not believe that is possible with out-of-the-box Jira Cloud. There may be something for sale in the marketplace to do it...or, you could build something using the REST API, and that might be much more complicated to do. __Bill

Hi @nat Where is your customer request type information stored? If that is in another field, you could use automation rules to assign based upon that information. Here is the documentation on automation rules: https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/ And here…

Hi @Alexander Turbov The methods you are using will associate the Jira issues and the branch, but not transition them through the workflow. You can use the automation rules to do that. Here are some example use cases, including moving your issues through workflow based upon development triggers:…

Hi @P B -- Welcome to the Atlassian Community! Noticing your prefix about Butler, are you asking a Trello question rather than a Jira Cloud one? If so, please consider posting your question in that area: https://community.atlassian.com/t5/Trello/ct-p/trello Best regards, Bill

Hi @Gui Ávila You cannot change these behaviors with out-of-the-box Jira cloud. Here are the suggestions to make these drop-down lists project specific, which you can view and vote for: https://jira.atlassian.com/browse/JSWCLOUD-11814 https://jira.atlassian.com/browse/JSWCLOUD-17465 Best regards, Bill

Hi @Gui Ávila Below is the suggestion to add the ability to bulk edit, assigning sprint by name rather than ID. You can review and vote for the issue: https://jira.atlassian.com/browse/JSWCLOUD-10651 Best regards, Bill

Hi @Pablo -- Welcome to the Atlassian Community! You could also use an automation rule to mark an issue as flagged when the due date is overdue, which will highlight it on the board better than card colors. For example: * Trigger: scheduled to run once per day * Condition: due date is overdue (less than or equal to today)…

Thanks for that information. I was suggesting the use of the log to confirm that the smart value was indeed parsing as you expected, particularly because this is a custom field. Now that you have verified that it works for one value for a specific trigger, try using the generic trigger again (field changed) and see what a…

Hi @Endre Kallai I cannot see an easy way to see which rules have not been run, only the ones which have. I added a suggestion to add this feature: https://jira.atlassian.com/browse/JRACLOUD-75574 Best regards, Bill

Hi @Jesse Maxwell I had an earlier support ticket on this, and I was told that Status Category Changed Date was implemented as string rather than as a date/time field for some reason. If you convert it first it should work: {{issue.statuscategorychangedate.toDate.mediumDate}} Last Viewed may have the same issue so try the…

If you mark that linked issue as either watch or "affects my team" you will be notified for status changes. What do you mean by "revert to the other Jira"? If you mean classic projects I believe that they have the same issue for cloning.

Hi @Michael Crincoli Please talk to your site admin about adding a custom field, which you can learn more about here: https://support.atlassian.com/jira-cloud-administration/docs/create-a-custom-field/ One you have the field available to the project, update your filter to remove abandoned items from reporting, such as…

Interesting problem... This seems to work (and it is convulted ;^) Let's say you wanted the 2nd Friday after whatever the current issue's updated date: {{issue.updated.endOfMonth.withNextDayOfWeek("FRI").plusDays(7)}} How this works: * Take the date you are interested in * Go to the end of the month using .endOfMonth * Go…

Hi @Maya.herman Are you still seeing this issue? If so, I have seen several other posts about possible causes: * Intermittent network issues to the internet * There is a required field for the issue, which cannot be entered with just the quick create * There is automatic assignment to someone, such as the Project Lead, and…

Hi @Tim Tidmarsh You cannot do what you ask with out of the box Jira, as that would require rolling up the log history data for different time intervals, over time. Here are some work-arounds/ideas: * You can get close for the daily counts by using the cumulative flow report, changing the time range, and disabling all…

Hi @Kaeru Here is the link to the ticket that removed it, so you may want to comment to ask for how to re-enable it: https://jira.atlassian.com/browse/API-343 And here is one of the many community posts leading to the disable, so you may find something in there too:…