Bill Sheboy Expert

Hi @Vishnu Vardhan Chenna Please create a new question rather than adding a different one to this older thread. That will help more people to see it to offer suggestions. And when you create your question, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an…

Hi @DS -- 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 provide context for the…

It is often better to have two (or more) separate rules for this scenario: * Detect field change, condition confirms the issue type is an epic, and then branch to the child issues (e.g., Story, Task, Bug) to copy the field * Detect field change, condition confirms the issue type is a Story, Task, or Bug, and then branch to…

As noted, the value attribute may be used for comparison. What are you trying to do, once each value is detected: * count issues with a value * something else? To count issues with a value, this would count the ones set to value "A" {{#=}}0{{#lookupIssues}}{{#if(equals(customfield_10209.value,"A"))}}+1{{/}}{{/}}{{/}}

For a selection field, there is a value attribute, such as this: {{issue.mySelectionField.value}} To confirm you have the correct expression for the counting, please answer: Is your custom field single selection or multiple selection? Are you trying to find issues where one of A, B, or C are selected, or all values A, B,…

Hi @Anatolii Borkhovych -- Welcome to the Atlassian Community! Adding to the other answers...that is not possible using that branch type. Branches which could be on more than one thing (such as on Subtasks) are executed in parallel and asynchronously. And there is no guarantee when the branch will complete, up to the last…

Well, that is surprising that custom formulas apparently do not support that for JPD: https://support.atlassian.com/jira-product-discovery/docs/expression-based-formulas/ I will strikethrough my incorrect suggestions above. Back to my initial suggestion: use a number field rather than a "custom formula" field, and an…

Update: the below suggestion does not work. As you are doing the calculation in a JPD custom formula for a field you only need to use the field name for the calculation. For example: {test number single select} * 3

Awesome; I am glad to learn that helped!

When you sum the original estimate to the parent issue field, and then show the Σ Original Estimate on the backlog, it is double-adding the values. For example: * the total for the Subtasks' Original Estimate is 110 hours * that value is set to the parent's Original Estimate field in the rule * and so the backlog displays…

That seems to confirm the fields are sometimes "confused" and sometimes not in the rules. I recommend checking some of those Bug issues types to confirm the fields actually copied as you needed, or if they have null values. For this rule, please try setting just those fields using their custom field ids and advanced edit…

Considering your issue hierarchy, if you manually create an issue of type Vulnerability with the UX page can you set the Epic Link field?

Thanks for clarifying! This could be done with a scheduled trigger rule and the Lookup Issues action to gather the issues: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Lookup-issues For example... * trigger: scheduled, daily, with no JQL * action: lookup issues, with JQL to find your issues…

Hi @Alexander Berlin -- Welcome to the Atlassian Community! Would you please show the configuration for your backlog fields, showing which fields are being displayed? Also, when you set the time tracking fields in that issue edit action, I believe you need to specify the units of measure, such as m for minutes, after the…

Hi @Kerri-Anne Mak Scenarios like this are context-specific, and your context will determine solution approaches... Currently, the rule uses an entity property to prevent duplicating the subtasks. To keep that approach, you would need multiple, different entity properties: one for in-progress and one for ready-for-QA.…

Hi @Valentina Migliore 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 offer…

Hi @koutarou ishibashi This question seems quite similar to your other question for performing counts with lookup issues, with the key difference being using subtasks: https://community.atlassian.com/t5/Jira-Software-questions/Ask-how-to-use-Lookup-issues-action/qaq-p/2626134 Please see the responses to that question to…

Hi @koutarou ishibashi You may use multiple Lookup Issues action calls, with different JQL; or use one call, and list iterators, smart value, list filtering and math expressions to do that: * https://support.atlassian.com/cloud-automation/docs/jira-smart-values-lists/#Combined-function-examples *…

Hi @Ariel Altaras One possible cause of that symptom is the Issue Created trigger can fire so quickly that some of the issue data may not be available for the rule to use. The work-around / fix is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow down the rule a bit,…

Hi padmalatha79@gmail.com I believe that is possible, however: what problem are you trying to solve by doing this? That is, "why" do this? The creator (i.e., reporter) and assignee already have fields in the issue, and so copying the same values into the Summary will lead to a maintenance challenge, requiring updates of…

Ryan, do you mean detecting specific changes in the Summary field to send the Teams message or that when the Status transition happens then the Summary field is sent? The first case cannot be detected with JQL. Instead a change to the Summary field can trigger the rule and then conditions could detect specific changes to…

Hi @Avinaba Deb -- Welcome to the Atlassian Community! Yes, there is. Please follow the documentation link above, and you will find information for the different format expressions (via a link to the Java docs). Kind regards, Bill

Thanks for that information. Would you also please post: * an image of your scheduled trigger's details, * an image showing the audit log details (i.e., show more) for an execution of the rule which had this behavior, and * for an issue which had this behavior, and image of that issue's change history Those will narrow…

Hi @Michelle Kha -- 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 provide…

Please try using the format() function: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/#format-input- Perhaps like this: {{#lookupIssues}}{{#sprint}}{{#if(equals(id.format("#"),"1239"))}}{{name}},{{/}}{{/}}{{/}}

Hi @Vivian Lau -- Welcome to the Atlassian Community! No, that is not possible, although it has long been requested. In my opinion, there are lots of display problems and data gaps on the Atlassian versions of the those charts. Perhaps investigate better versions of the CFD and Control Chart in the marketplace as addons to…

If you wanted it as people-friendly, such as "2d 4h", the custom field would be text type. I would need to see the specifics how you are setting the field to comment on any problems with the value (if a text field does not work).

Hi @Elizabeth Butler No, unfortunately not yet. Here is the open suggestion to change that, which you may vote for / watch to see progress: https://jira.atlassian.com/browse/JSWCLOUD-21257 Kind regards, Bill

Hi @Waldispühl Armin Do you mean that you have many filters, and each label is noted once per filter? Or instead perhaps there are many filters, and many reference the same label? If it is the second case, you could reduce the number of filters requiring updates by chaining them. For example...Let's assume you have these…

Hi Richard, and welcome to the Atlassian Community! Yes, and...to the answer suggested: Are you using a company-managed or team-managed project? You may find that information at the bottom, left side of the page expanding area. If you are using a team-managed project, there are known problems with the CHANGED operator in…