Bill Sheboy Expert

Based on that, there are multiple versions for the project. Epics and Stories can only have one version value in their Fix Version field. Issue Version 1.0 Version 2.0 ======= =========== =========== Epic A X Story 1 X Story 2 X Epic B X Story 3 X Story 4 X If this is correct, you could use either JQL example I suggested,…

Hi @Talles Silva Unfortunately automation rules, like many features of Jira boards, do not use the non-working days customers configure for projects. There are lots of suggestions to improve this with Jira, including for automation rules. The only work-arounds I know for this symptom are: * When incrementing by business…

Yes, the JQL would change to handle a list of versions, to use the IN operator versus the equals = operator Before making that change, would you please clarify your scenario? Fix Version is normally associated to a release version, even though Jira allows multiple values in the Fix Version field for cases like multiple…

Hi @Aidan Follestad -- Welcome to the Atlassian Community! Have you considered having different epics (and so with different component values) for each platform? That would eliminate the need to determine the maximum sizing / sum by platform. Without knowing your Jira version (Cloud, Server, or Data Center) I wonder if you…

Hi @Team GoCredible -- Welcome to the Atlassian Community! As this is quite an old thread, I recommend creating a new question and linking back to this one. That will ensure the most number of people see it to offer ideas. When you create you question, please post an image of your complete automation rule, images of any…

One of the challenges with smart values is the are often slightly different than the field names used in JQL... in JQL fixVersion is used and in the smart values, it is plural: fixVersions Please change your two JQL statements to use this: {{triggerIssue.fixVersions.name}} And please note: this will work if you have one,…

Thank you for that information, @Wojciech Wardaszko as I was not aware the publicly available, REST API functions supported that capability.

Damien, let's confirm you are looking at the system admin view of the filter list. Please try this one directly, substituting in your Jira URL: your Jira URL/secure/admin/filters/ViewSharedFilters.jspa That should indicate System - Manage Filters at the top of the page. If you do not see that, please ask one of your peers…

That recursive transition may be the cause, and the "work-around" from the support team may not be helpful for some teams as it states to remove the loop. Perhaps work with your site admin to contact Atlassian Support to learn if they have any other work-arounds or suggested fixes: https://support.atlassian.com/contact/#/

Comparing your board's filter and the placeholder issues, added as children to the epics, would they display with that filter?

Thank you for the additional details, Quentin. Some things I notice in that information... Are the founders you note, who are providing the "deadlines", also coding with the team? If not, I find when people who are not doing the work provide the forecasts, they can be disconnected from the facts on the ground, and…

That was my mistake, which I corrected in the earlier post: the comparison in the JQL should be to {{triggerIssue.project.name}} The reason is sometimes automation smart values use the default field / attribute (e.g., the key for an issue) and sometimes they return the entire object. In this case, it appears to return the…

Hi @Damien Bastogne -- Welcome to the Atlassian Community! Adding to Michel's answer... Before you delete a filter from another user, you may want to check the sharing of the filter. Others could be using that filter, and knowing that before deleting it may lead to other choices: changing the filter owner, combining other…

Hi @Benedikt Ostwald -- Welcome to the Atlassian Community! Adding to Walter's answer... In my experience, one of the challenges of making a board column / status for a "blocked" condition is blocking becomes a normal condition to the team. And so teams are less likely to work toward reducing it in the future; instead they…

Dynamically doing this with the Lookup Issues action, and the JQL branch to find the epics, is what I was suggesting: everything is relative to the trigger issue's project and fix version. An example rule could be like this: * trigger: issue field changes for Start Date or Due Date * condition: issue type equals Story *…

Hi @Leonardo Zevallos Guzman 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 provide context for the community to…

Hi @Lara Sousa When do you need to add the additional text? Knowing that will help decide what trigger your rule should use. When you have an issue in the rule, you may add to the field by editing the issue, selecting the Description field, and add the new text to existing smart value. For example: {{issue.description}}…

Hi @Quentin Ceulemans I am unclear how your team is using these date fields to assess progress. Perhaps if you clarify the team's practices the community will have more information to make suggestions. For example... Often teams forecast the effort to complete a specific work item during intake and / or backlog refinement.…

Hi @Michael Caplan There could be several causes for what you describe. I recommend adding writes to the audit log as the rule proceeds to check them. And you can try these diagnosis steps. * You note your rule is "site wide". By that do you mean the rule is global in scope, and if so have you determined that the version…

Hi @kenan xin -- Welcome to the Atlassian Community! I have not tried that with this smart value, so please experiment to learn if this helps: The {{build}} smart value is only available with the built-related triggers: Build Successful, Build Failed, or Build Status Changed. And so the rule will need to use one of those.…

Hi @Ilja Thieme What you are showing appears to remove the completed / done status values from display...and thus it is no longer a CFD. Is that correct? Regardless of that situation, and back to your question: There is an old, open defect for this symptom of negative issue counts when the issue workflow contains recursive…

Hi @Pulkit Sharma -- Welcome to the Atlassian Community! That is a known defect; you may vote / watch this item to see any progress: https://jira.atlassian.com/browse/AUTO-762 A possible work-around, depending upon your tool receiving the email, is to send the field as text and let the URL parse. For example, this will…

Given this symptom appeared after the board / backlog enhancement went live, and you are on a paid, Jira license, I recommend working with your site admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/ The admin will need to submit the ticket, and they can add you as a contact to…

Thanks for that additional information. The challenge with this scenario is the description field needs to be stable enough to create a match() expression to check it. Let's assume your description also contains the questions, as you show, and that each one always ends in a question mark. The first step of the parsing to…

I am unclear what you are describing, other than a person logged work incorrectly. If the prior worklog entries need to be edited the person who logged them will need to make the changes.

You describe wanting the action of adding the comment on issue transition to another status, but the rule is triggered on a scheduled trigger. Have you considered using the Issue Transitioned trigger instead? Or are you instead wanting this rule to trigger when a transition has not occurred? Please post images for both…

Hi @Anna Naidenko -- Welcome to the Atlassian Community! You note that the Jira project is "sometimes used by other teams". Is their usage frequent enough that it would warrant creating a separate Jira project for them, eliminating the impact on your team? Kind regards, Bill

Hi @Márton Kelemen What is your relationship to the vendor of this product? In accordance with the community guidelines for marketplace and solution providers, please ensure you disclose in the text of your post your relationship to a vendor when recommending their products. Please see the community guidelines for more…

Hi @大角　竜央 -- Welcome to the Atlassian Community! When you tried to publish your automation rule, you observed this error message: "The rule could not be enabled. Please check your rule settings and try again." The cause is one or more of your rule components has an error. This could be a missing, or invalid smart value,…

Hi @Shweta Katore -- Welcome to the Atlassian Community! What you are describing seems to be something external to Jira. Is it Microsoft Sentinel Playbook? If so, please look at the documentation for that product, or its connector, for support. Kind regards, Bill