Bill Sheboy Expert

Hi @Shiwanshu Singh -- Welcome to the Atlassian Community! Please find an example issue where the field was cleared and then review the issue history. That may explain what (or who) cleared the value from the field. Kind regards, Bill

Awesome; I am glad to learn that helped!

Hi @Oksana Oliinyk That is not possible with the built-in formula feature of Jira Product Discovery (JPD) fields. One workaround is to use an automation rule to perform the calculation (when the source fields change) and then round the result into a custom field. One limitation of this approach is it cannot use other…

Hi @Sonu kumari There is limited summing capability for dashboard gadgets and the built-in reporting for project boards. There is no generic "sum any field" capability. Some possible workarounds include: * exporting issues for reporting in external tools * using the REST API to pull issue data into external tools * using…

Hi @Natalie Franklin For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image, * images of any relevant actions / conditions / branches, and * an image of the audit log details showing the rule execution. Until we see…

Hi @Suvarna Just following up to check if John's suggestions answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks, and kind regards, Bill

Hi @Michel van de Wiel Just following up to check if the suggestions answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @Shahid Meman Just following up to check if this answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @Rustam Hasanov -- Welcome to the Atlassian Community! Just following up to check if Trudy's suggestions answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule…

Hi @Francisco Navarro Just following up to check if John's suggestions answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks, and kind regards, Bill

Hi @Kieran Fisher Just following up to check if John's suggestions answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @Susan Hamilton Just following up to check if Trudy's suggestions answered your question. If so, please consider marking this one as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @Bachir AMMACHE Just following up to check if this or Kelly's response answered your question. If so, please consider marking them as "answered". That will help others with a similar need find solutions faster. If not, please let the community know what help you need with the rule changes. Thanks!

Hi @Naresh Rajak That measure is sometimes called the "Age of WIP", and there is nothing built-in to measure it. There are marketplace apps for such time-in-status tracking (reading the information from the issue history). Or you could use custom fields and an automation rule to help. For example, let's assume an issue…

Hi @Kawa Akbulut -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image, * images of any relevant…

Hi @Jessie Sodolo I believe that is based on using issue links with a type of "Blocks": https://support.atlassian.com/jira-software-cloud/docs/understand-insights-on-the-board-in-company-managed-projects/ Kind regards, Bill

Hi @Josephine Turner In the Send Web Request action, there is an option to continue processing after an error: Continue running the rule even if the request response is not successful (i.e. non-200 response) When that is enabled you could use the response code with conditions to decide next rule steps. Kind regards, Bill

Hi @Aaron Pavez _ServiceRocket_ Just following up to check if that worked with your testing. Thanks!

Thanks for checking that, @Stefan Salzl This apparently shows the object's attribute is similar to other rule smart values which are loaded just-in-time by additional REST API calls. (e.g., {{issue.subtasks}}, smart values from marketplace apps, etc.) Because of that, there was a timing problem where the value was not…

You may want to chat with your Jira Site Admin for help; they may have more experience with rule-writing and could offer coaching, or perhaps even create the rule for you.

Hi @Tushar Khandelwal -- Welcome to the Atlassian Community! Adding to Marc's suggestion: Using the information from the same link Marc provided, you may add the ROUND() function around the expression to use the desired precision. For example: {{#=}}ROUND({{issue.Total value}} * {{issue.Total Alignment}} / {{issue.Total…

Hi @Martin Flury Your rule image shows using the Assignee for the Send Email action, but there is no issue within scope at that point in the rule. The fix is to add a branch to most-recently-created-issue before the email action: * trigger: scheduled * action: create issue for the task * branch: to most recently created…

Hi @Saad Ahmad and @Jack Brickey I found several open suggestions related to changing / consolidating the column sort order, including by workflow: Allow for customizing 'Two dimensional filter' column order Two Dimensional Filter Statistics gadget should allow sorting of values as configured in select list custom field…

Hi @Damian Trutkowski -- Welcome to the Atlassian Community! Please note for JPD project rules involving their date fields: As you see, JPD uses its own, text-based "date" values. These can represent a single date, a date range, a month, quarter, or year. As both of your fields appear to be JPD "date" fields, they can be…

Hi @l.seplecan Adding to the answer from @Tomislav Tobijas Sadly, that automation library (formerly called the automation playground) has become neglected for well over a year, with broken links as the rules were renamed / recreated or deprecated due to feature changes. I just did a quick check and even the rules I…

Hi @Vani V Bhat -- Welcome to the Atlassian Community! With Jira Cloud, when using the built-in feature to move an issue from one project to another the comments are moved correctly. How are you performing the "move" and what are you observing? Kind regards, Bill

Hi @Michael de Marigny I recommend using a Lookup Table for a scenario like this: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798 This would greatly simplify the rule and make maintenance easier / safer. For example: * trigger: issue created * action:…

Thanks for that information, and regarding your response: I wonder if there is a for-each loop or a conditional statement ahead of it that can check if a given linkage between two issues already exists, and do nothing in those instances to avoid the endless looping. Rule branches which could be on more-than-one-thing are…

Hi @Amit Tandon -- Welcome to the Atlassian Community! That gadget only allows selecting fields with discrete values, not time tracking or number fields. Those would have an infinite number of values and so could not be displayed one-by-one on an axis. The built-in reports for time tracking are quite limited, so please…

Hi @Derek LoGrande -- Welcome to the Atlassian Community! Such scenarios are challenging, risky, and brittle to manage with Jira and automation rules. Please consider: * Edge cases (e.g., what to do when a Main Account Number is changed such as from an entry error) * Cross-linking errors (e.g., A -> B -> C -> A) causing…