Bill Sheboy Expert

Hi @Rahul Mittal Based upon that image, you are using Jira Data Center. Is that correct? If so, the Lookup Issues action in Jira Data Center automation will not work for this scenario because it only supports a limited number of fields at this time. Please see this post describing how to access the other fields, and…

Hi @Pedro Iván Márquez Peña This scenario is difficult for Jira Data Center automation as it does not yet support Advanced Branches: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749 At this time, the only workarounds I know are: * When the team is using Scrum, rather than other practices, use the Daily Stand-up to…

Hi @phebean Atoyebi -- Welcome to the Atlassian Community! In addition to the 100 issue limit noted by other suggestions, another way to get the counts is using smart value, list filtering and a math expression: * https://community.atlassian.com/t5/Automation-articles/Filtering-smart-value-lists/ba-p/1827588 *…

Hi @Brian Husk -- Welcome to the Atlassian Community! Yes, that sounds correct. To get the version's ID, your rule could use the Version Released trigger and then make the call to the REST API endpoint using the Send Web Request action:…

Yes, and... The plural {{issues}} smart value is only supported for Jira Data Center's bulk-handling feature, not for Jira Cloud automation. (Although experimentation I did years ago showed it does return unpredictable "stuff" when used in a Cloud rule :^)

Well done, and I am glad to help!

Hi @John DiMaria Though I do not recommend translating quantified-measures to relative-sizing ones, you may want to try using a Lookup Table rather than a complicated conditional expression. That will be much easier to maintain and understand. Please look here to learn more:…

Hi, @Jack Brickey Without seeing the specifics of your rule's Edit Issue action, that seems to indicate the custom fields are not available for the issue. First, I would use an example issue to confirm they are supported, and the exact smart value / custom field ID for the…

Hi @Sahir Maharaj -- Welcome to the Atlassian Community! Jira Cloud license level has no impact upon the behavior of the Manual Trigger, or user inputs, for automation rules. To learn which features only apply to specific products, or license levels, please see the documentation. For example, the SLA-related triggers only…

Hi @Thomas Schenkel 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, * images of any relevant actions / conditions / branches, * an image of the audit…

Hi @Susan.Welsford -- Welcome to the Atlassian Community! There is limited display of that newer / additional information for releases. I believe it is only shown on the individual release page (or by reading it with the REST API endpoint). Are you asking about displaying it in the list of releases view? If so, I do not…

Hi @Russell Haynes -- Welcome to the Atlassian Community Without seeing all the issues involved and the settings for the Control Chart, I suspect some of them are being excluded by the chart settings. I recommend identifying a specific issue found by the filter but not shown on the chart and then review what is different…

Hi Anahit Sukiasyan, Once again, do not post bot / AI-generated content without disclosing the source. Please carefully read the community guidelines as you continue to do this: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Additionally, the automated answer you posted cannot work for Jira Data…

Hi @Vineela Durbha Please see this article and post for summing fields to a parent. As you are using Jira Data Center, the REST API must be used to sum the time keeping fields because they are not yet supported by the Lookup Issues action.…

Hi @Rob Rademeyer -- Welcome to the Atlassian Community! First thing, what problem are you trying to solve? That is, "why do this?" The rule steps you describe could more quickly be done by manually adding / removing the label, so knowing what problem this solves may help the community to offer better suggestions. Until we…

Hi @Kit Friend Although I agree with the idea of documenting shared non-functional requirements (NFR) in a human-readable location (e.g., in Confluence) independent from the work items (e.g., in Jira), that may lead to "out of sight / out of mind" behaviors, except for new team member onboarding, project liftoffs, and…

Hi @Anahit Sukiasyan As a reminder, do not post bot or AI-generated content / answers without disclosing the source. For more information, please read the community guidelines: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Kind regards, Bill

Hi @gordon.varney Adding to Trudy's suggestions: Your rule has multiple Edit Issue actions. Those changes potentially walk-over / collide with earlier saved data as actions use the current state of the issue in the rule's storage for the edit (and not what is stored in the cloud). This is intentional and is not a defect in…

Hi @Heidi Vanderholm With the built-in dashboard gadgets, you could use the Two Dimensional Filter Statistics to display the specific Epics, and visually observe / count them. For example, create a saved filter using your board filter as a starting point, adding some additional criteria: yourBoardFilter AND issueType IN…

Reading your original rule images, I notice some things that would cause problems: Lists use a 0-based index in rules, and so the parameter to the get() should be a 0 and not a 1. However, that is not needed when the branch is changed. Assuming you are trying to add the issues and tasks under the trigger issue, please try…

Correct; for the scenario you show you may want to try the global or multiple-project scope rule and add the conditions / branching needed to access the correct issues.

First thing, you may want to read this article from @Trudy P Claspill on automating the shifting of dates for dependent, linked issues. There are some "gotchas" to be aware of, such as I noted in my original post for this thread.…

Thanks for that information, and as I described the REST API would be needed to access those fields and update the parent issue. Please see the linked post for details. When you only need to report on such issues, and not edit another issue, the bulk-handling feature of branches and scheduled triggers may be…

Dick, my searches / testing indicate v1 is the latest (and only) version of the Teams Public API. Do you find a newer one? Thanks, and kind regards, Bill

Hi @Sebastian Pechhold Please see the above posts about the differences for projectTypeKey and typeKey with the REST API endpoints, and then contact the vendor of that third-party tool to ask them about making adjustments to support pulling JPD data. Kind regards, Bill

Jack, I updated my first post to match your findings...just in case people stop reading too quickly and get puzzled by the results. Thanks, again!

Hi @Rees, Ian Short answer: based on what you show, there is no solution because the first table shows a many-to-many mapping of values-to-categories, and so multiple values could be returned with the same rank-hierarchy value, but only one is possible for a single-selection field. Slightly longer answer, assuming there is…

Hi @Vincent Dufour 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, * images of any relevant actions / conditions / branches, * an image of the audit…

Hi @Leyla Kinaze You appear to be using the incorrect smart value for Fix Versions, as it is plural (and provides a list of the versions for the issue). Please try this: {{issue.fixVersions.startDate}} If that does not work, the cause for Jira Data Center could be the attribute is not supported by the issue REST API.…

Hi @Lakshmi Kumari That appears to be a team-managed project and the Issues list, basic view. Is that correct? Are you the only person on your team seeing this symptom or is everyone seeing it? I wonder if there is something "stuck" in the browser page data after the field changes. Perhaps try these things: * refresh the…