Bill Sheboy Expert

Hi @Fahad Mubarik I recommend trying to create an automation rule, triggered on Sprint Completed, and then use the Lookup Issues action with JQL to gather the issues in the sprint. With those, you can produce the counts you describe. To get you started on creating your rule, please refer to these documentation and example…

Yes, that is aligned to what I was suggesting. Although the JQL is incorrect: when referencing issue fields just use the name without the "issue." prefix. project = yourProjectName AND duedate < now() AND status != Done I recommend testing by running your first rule with some examples to set the due date and then running…

Hi @Sidharth verma First thing, this is an older thread and so I recommend creating a new question to increase the visibility for the community to offer ideas. When relevant, include a link back to the order question / thread for context. Back to your question... If you are branching on AQL, that is returning the list of…

Adding subtasks for only the newly added values to the Fix Versions field may not work. The reason is the changelog available to automation rules is not always accurate: https://jira.atlassian.com/browse/JRACLOUD-80486 You could still try it to learn if it meets your needs with the field change smart values for added…

Hi @Victor - Modus Create As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see: Atlassian Community online guidelines | Marketplace + Solution Partners | App Central…

Hi @Petar Cvetanovic First thing, "project" already has a specific meaning in Jira, and so creating an issue type with that same name may have unintended consequences (e.g., cause confusion, lead to automation rule or JQL errors, etc.). Please use cause in automation rules to confirm the context is correct when checking…

Yes, it is a list element, as text, and so the names of the components is this: {{webhookResponse.body.fields.components.name}} Using the components element directly in the edit likely does not work because the type is not recognized. You may make the dynamic JSON for the edit by iterating over the values: { "fields: {…

Hi @Sara Pfannkuchen -- Welcome to the Atlassian Community! A query like that is not possible with out-of-the-box features of JQL, and so it could not be detected for card colors with JQL. As workarounds, you could... * investigate marketplace addons for JQL to learn how they might help, or * try using automation rules to…

Hi @Alan Alder You have already asked this question while working through the challenges in another thread: https://community.atlassian.com/t5/Jira-questions/Jira-automation-craate-table-of-linked-issues/qaq-p/2753799 Kind regards, Bill

Please post the expression you are trying. That will help to diagnose what is happening. As an alternative to the dynamic elements, you may instead repeat the conditional blocks inside of the iterator. {{#issue.issuelinks}} conditional block to test for "delivers", and add a row conditional block to test for "depends on",…

Hi @Guy Slade When setting the components with JSON in a rule, please try the array syntax: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Components As you are getting the data from the webhookResponse, first check if that is a list or an array by writing the value to the audit log.…

The or() clause needs to wrap around the equals() tests for each type, as the equals() is what performs the test: {{#if(or(equals(field, valueA), equals(field, valueB)))}}display when true{{/}} Please note well: you are now mixing link directions in the expression, inward and outward links. And so the logic to include the…

You could use the OR() conditional syntax, with two equals() calls, testing the different values. Then add an additional column for the link type in the table. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#or

Oops...missing a newline after the conditional to trigger the new row. I updated the earlier post.

Hi @Alan Alder -- Welcome to the Atlassian Community! You are iterating over the issuelinks inside of the table row formatting. Try moving the iterator outside of the row's conditional check. For example: *Delivers Tickets* ||*Ticket*||*Status*||…

Hi @Guy Slade -- Welcome to the Atlassian Community! I see two things to adjust in your rule: First, a created variable is plain text, and when the labels are added, by default the list flattens out to a comma-and-space separated values list. To feed them into match(), they must be split back apart with split(", ") into a…

Ah...now search on the page for "customfield_11228" to see if it has a value further down the page. That will show the format to set it, when possible.

Awesome; I am glad to learn that helped. To make the rule logic clearer to someone reading it later, it may help to rename the variable to varNull and the test value to "Null". I will update my earlier post to match that.

Hi @[deleted] -- Welcome to the Atlassian Community! That is an incorrect assumption. It is possible to set the Start Date, or other fields, using various methods, such as workflow or automation rules. From what you described, using automation rules may be better as they could be triggered on Sprint Started or changes to…

Hi @Marc Schadee First, your syntax is not quite correct for that version of if: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#if {{if(smartValue, "value if true", "value if false")}} Yet even with that adjustment, it will not work due to the null value collapsing the expression.…

Hi @Elliott Lock I do not believe the scenario you describe is easily possible with Jira Data Center automation in one single rule. The reasons are: * triggers, branches, and lookup issues can only reference up to 100 issues at a time * I do not believe advanced branches (over things other than issues, such as assignees)…

Hi @Hiya Garg -- Welcome to the Atlassian Community! Adding to John's suggestions... It is likely when your rule runs and sends the email, that needs to be recorded somewhere in the issue. For example, using a custom field, comment, label, etc. Then a second rule could run daily to check if there has been no activity based…

Hi @Uwe Pilz Some fields of a parent issue are visible to the child, without any lookups. That includes the watchers. And, when adding the watchers from one issue to another, they can be added by referencing them directly. Putting those together, you could simplify your rule to this: * trigger: issue created * action:…

Ah, that helps clarify things! Some addon / plugin fields are not supported by automation rules as they are dynamically generated. To check if your field can be set by a rule, please use this how-to article to find the apparently supported fields for…

Hi @Chris Rosendorf When you have a very long rule to post, you can try a browser addon or separate app to capture the image with the page scrolling. Back to your question...and without seeing your rule for context... Rather than branching over the issues you could try: * use a lookup issues action with JQL to gather them,…

What are the saved filters for the two different boards?

Hi @Guy Anela Yes, that is one of the open defects. I could not find the other one. The symptom for the Sprint field appears to also occur because there are multiple paths to create (and assign) a sprint, and some do not consistently work (for changelog returns). e.g., from backlog, from sprint completion, etc. Thanks…

Hi @Guy Anela Thanks for that suggested approach. And as a heads up... The changelog entries which automation rules can see for list fields like Sprint are not always accurate. (e.g. {{fieldChange.from}} ) I recall there is open defect for this and the Fix Versions and Affects Versions fields. For your second rule, this…

Is that field on your create issue screen for that issue type?

Hi @Mireya Cintora -- Welcome to the Atlassian Community! In the Edit Issue Fields action, when you select a field you may often select to Copy from Parent Issue in the options at the right side of the field. If that does not help, please create a new question, including images of your complete rule, the Edit Issue action,…