Bill Sheboy Expert

Hi @Caroline_Muon That is not possible yet. Please see this other question with the response from the JPD team: https://community.atlassian.com/t5/Jira-Product-Discovery-questions/Exporting-Data-in-Jira-Product-Discovery-issues-with-Formula/qaq-p/2248594 Kind regards, Bill

Hi @Paul Thompson -- Welcome to the Atlassian Community! Short answer: that is not possible with built-in dashboards, but there are several possible workarounds. Some possible workarounds are: * use a marketplace addon / dashboard * use chained, saved filters * use automation rules to dynamically update the saved filters…

Hi @PION-DRANCY François The NOT IN operator should work for a query with the status field: https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#NOT-IN For example: project = myProjectName AND status NOT IN (Done, Archived) Please post the exact JQL you are using which is not working as expected. That will…

Awesome; I am glad to learn that helped!

Hi Artur Balyan @ Immedis Adding to the other suggestions offered... The watchers field is a list of users, and when this smart value expression is used in the Send Email action's To field: {{issue.watchers.emailAddress}} By default, it joins them with commas. However, the Send Email action uses a semicolon delimiter…

Hi @Kaja Iske You could check the fields in {{destinationIssue}} with a condition so the rule only proceeds when they have values: https://confluence.atlassian.com/automation/jira-automation-triggers-993924804.html#Jiraautomationtriggers-issuelinkedIssuelinked Kind regards, Bill

Hi @Ragavendran S Subject to the details of your scenario, you may be able to implement this using a Jira Automation rule. The rule could use a scheduled trigger to check the issues daily to set / clear the flag. I recommend trying to create your rule, and if you run into challenges, post images of the rule and audit log…

Team-managed projects (TMP) are a more recently added set of features to Jira, and differ in many ways from company-managed (CMP) ones. And so the underlying code appears to differ to support those things you observe (and creates some incompatibility with other Jira features). The TMP target audience is for teams managing…

Hi @Lukas Harrer -- Welcome to the Atlassian Community! Short answer: the page needs to be refreshed to update the timeline view for that scenario. As a disclaimer, I am just another Jira user and have no specific knowledge of the internals of the application(s). There are some things in Jira Cloud which dynamically update…

Hi @Smitha Joseph In my opinion, "no". There is always uncertainty related to the work requested, the solution approaches the team selects, any forecasting / sizing of work, emergent business priorities, technical impediments, and certainly, the people-related things: * availability of people on the team * shared…

Hi @Rajmohan Maudshetty -- Welcome to the Atlassian Community! Where in Jira Cloud are you observing an indicator of sprint predictability > 100%? Please post an image of the page view which shows this. That may provide more context for the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Cash Coyne I do not believe that is possible with the built-in JQL... The EQUALS = operator is not supported for such fields and the CONTAINS ~ operator uses fuzzy matching, even when the exact match syntax is used. (e.g., summary ~ "\"123.456\"" ) Depending upon your scenario details, you could try an automation rule…

Hi @Maurice Stassen You could try the Create Variable action to do that: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-variable There are some limitations on when / where a value can be set and later used in a rule. And so if using that action does not help, please post images of your…

Thank you for clarifying, as that is the list / issues view from the other project types (and not Jira Work Management). Many fields cannot be edited inline yet in that view. And, that view is relatively new and evolving quickly. I recommend watching / voting for these suggestions to add more fields for inline edit, and…

Hi @Raymond A Rondeau -- Welcome to the Atlassian Community! Are you trying this with the List view in a Jira Work Management (JWM) project? If so, I just tried that and it worked for me for the built-in Start date and Due date fields with both a company-managed and team-managed JWM project. Would you please post an image…

Hi @Morgan Watts Although many common scenarios can be solved by both Jira Automation and Workflows, in my understanding of both, there are distinctions in what is supported. A few such distinctions are: * workflows can have validators before an event / transition proceeds and actions before or after the transition *…

Hi @Keyshla Coriano Parrilla -- Welcome to the Atlassian Community! Adding to Trudy's suggestions... You appear to be using Jira Cloud. Is that correct? If so, the Epic Link field is sunsetting and the correct field to use now (and in the future) is Parent. Your original rule which creates the child Stories and Tasks could…

Hi @Christine Green I believe that is possible, and... If you mean a built-in checkbox field, the rule could be triggered by a change to the field, and then add a condition to check the value before the issue edit. If you mean a checkbox field from a marketplace addon / app, please check the vendor documentation to learn…

Hi @Emily Luehrs -- Welcome to the Atlassian Community! Does your Jira Work Management (JWM) project form create a Jira issue in the project? If so, you could try an automation rule, triggered on issue created, to perform the assignment. The key will be to identify the source of the issue was a form. I believe a label is…

Are you trying to clone the issue into the same project as the trigger issue or a different project? And if it is a different project, is it to a Jira Product Discovery (JPD) project? If so, that is a known problem and the error may be ignored: https://jira.atlassian.com/browse/AUTO-175

Hi @c.ermeier Adding to the suggestion from @Vikrant Yadav ... What type of project are you using: company-managed or team-managed? Company-managed projects use the smart value Story points and team-managed projects use Story point estimate. Please adjust your smart value expression, as needed. Kind regards, Bill

Did you check if the Scheduled Trigger has JQL? If it does not, that is the cause.

Hi @Michele That new error message is from the recent change to validate rule components before the rule is published. What it should indicate is when an action, condition, or branch attempts to access issue data AND there is no current issue available to the rule's context. I have already encountered several problems with…

Thanks for the rule and log images to confirm the scenario. It appears you will need the REST API method to do this. Before you proceed, I recommend trying this to confirm the field is available: * using an example Initiative such as FS-7, call the REST API get issue endpoint by entering this URL in a browser tab…

First, the rule you show is comparing a single issue's fields to that issues subtasks. But earlier you noted checking this for "linked issues". Do you in fact want to check the subtasks? Next, I noted earlier that some issue fields are not loaded for Lookup Issues. The same is true for the subtasks smart value. Please try…

Hi @Mohammed Ansaar -- Welcome to the Atlassian Community! That new error message can be a bit confusing...what it indicates in this case is the rule uses actions which need issues but the trigger did not supply any issues. Please check your Scheduled Trigger as it appears to be missing the JQL to supply the issues. Kind…

Hi @Guy Slade -- Welcome to the Atlassian Community! First thing, I am using Jira Cloud, not Jira Data Center. And so my suggestions are based on what I know about automation rules, in general. With that out of the way... Context is important for automation rule questions. Please post an image of your complete automation…

Hi @Francisco Ochoa Di Iorio -- Welcome to the Atlassian Community! For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will…

For that expression, I believe that is the behavior when it detects noOfIssues is either 0 or empty, the same as this: noOfIssues AND LeadTime / noOfIssues If you replace the formula with just noOfIssues does it return what you expected or 0? That may narrow down if it is finding another value, or if the value is not yet…

Hi @Umesh Kulkarni -- Welcome to the Atlassian Community! First thing, I am not currently using Structure and so my suggestions are based on what I recall. With that out of the way... Have you tried adding a conditional to confirm the formula is detecting a non-empty value? Perhaps like this: IF noOfIssues: LeadTime /…