Bill Sheboy Expert

Hi @Lech Are you doing this with an automation for Jira rule? If so, have you tried: * Using dot-notation to access the fields? For example: {{webhookData.issue.key}} to get the issue key? * Using text functions, such as match() with regular expressions to extract the values? Kind regards, Bill

Hi @Natalie Al-Delemi Your rule shows branching to the current issue, and not branching over the objects (or smart values). And so it would only create one new issue. I am not using Jira Server, and so I cannot check this, but I do not believe Jira Server automation supports branching over anything except issues. Please…

That is curious that the type is unknown. I am not using JSM, and so I wonder if this is a dynamic field, calculated just-in-time for usage, which then prevents use in the branch. The way to check this (and solve your scenario need) is this: * using the Create Variable action, save the field value, which will make it text*…

Hi @Ilidio Faria What is your license level: Free, Standard, Premium, or Enterprise? If you are using Free several of the marketplace addons are free for 10 users or less. What are the missing features / better design elements you are seeking for the burn charts? Kind regards, Bill

Hi @Ivan Mizzi Your rule is using the Lookup Issues action, with an iterator over the values: {{#lookupIssues}} ... {{/}} Once inside of the iterator, the prefix of issue, such as with {{issue.some field}} is not needed as the scope is now the iterator (i.e., lookupIssues). Please try removing the prefix and re-testing.…

Hi @sanny.you -- Welcome to the Atlassian Community! For team-managed projects, the swim lines are set using the Group By option on the board view: https://support.atlassian.com/jira-software-cloud/docs/get-started-with-team-managed-projects/#Choose-the-best-view-for-your-board Kind regards, Bill

Hi @Rebekka Heilmann _viadee_ What is the type of your custom field: text, multiple select, something else? Some field types need to use the split() function to turn them into a list for processing by the branch. For example: * a text field containing: A,B,C * would need to be split with this to be used:…

To reset a bit, I just re-read this conversation thread from the beginning, and I noted you are using Jira Data Center...Custom fields are not yet supported for Lookup Issues with that version of Jira automation: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 When the Lookup Issues action was implemented for Jira…

I'm using Jira Cloud, and the default actor is always Automation for Jira. That appears to be different for Jira Server, and so I recommend leaving it as the default...whatever that value is. It makes no sense to me that the rule would not trigger at all if you are creating the issues in the same project as where the rule…

No: the rule should trigger when any issue is created, and the conditions are what limit which actions are performed. This new information may indicate a potential problem with either permissions or the rule's internals leading to a broken rule. We can check each with this: Permissions...I see you have changed the Rule…

Thanks for that information, although the puzzling part is still why the rule does not trigger. While in the project where the rule is defined, if you create a story (not a subtask), does the rule trigger? If not, please show an image of the Rule Details section, as that may indicate why the rule does not start.

Hi @Tom Scoggin Short answer: no, that is not possible. Once inside of an iterator, an automation rule cannot "see" anything except at that scope, and lower. It cannot see other issues, variables, or even data at a higher scope within the same issue which is the source of the iterator. My understanding from other posts is…

Hi @Paul Casillas What problem are you trying to solve by doing this? Knowing that may reveal other solution approaches. Thanks! Until we know that...You could do exactly what you asked in several ways: * with saved JQL filters and subscriptions to receive emails, * with an automation rule and a scheduled trigger* This…

Hi @Michael Bell Perhaps try a test call, observe what is in the response message to learn if it helps, and if does try saving it with Create Variable for subsequent calls within the scope of that one rule's execution. If you are instead describing subsequent calls for a different execution of the rule, the value would…

This depends upon the field type... * For number and text, just use the custom field id, such as: {{customfield_12345}} * For a select list, add the value attribute: {{customfield_12345.value}} I am using Jira Cloud, and not Server / Data Center, so please check your field type and attributes to confirm them. This how-to…

Let's try the simplest thing that should work first...Create a test rule to just list the values: * trigger: manual * action: lookup issues with your JQL * action: log the field with this: {{#lookupIssues}}{{customfield_13892}}; {{/}} Run that and review the audit log. What do the values show: with commas or decimal…

Once inside of an iterator, do not add the issue prefix as the scope is the iterator (not a single issue). {{#webhookResponse.body.issues}} {{key}} {{/}}

I cannot think of a reason that Rule 2 with the Issue Created would not trigger if you are manually creating the subtask in the same project as where the rule is defined. Let's confirm some context: * What version of Jira are you using: Cloud, Server, or Data Center? * What type of project is this: software, business,…

Have you tried iterating over the issues, such as with this: {{#webhookResponse.body.issues}} access your fields by the smart values {{/}}

Thanks; I missed that part, as it would certainly cause that symptom. Your audit log image shows a configuration change in the rule between what I assume was the successful run at 11:54:04 am and the incorrect one at 12:02:39 pm. You note the change was inconsequential; what changed? Another way to test if those links are…

Hi @Glen Cochrane Looking at your rule and audit log images... Is this rule defined in the ZPT project, or as a global rule with multiple-project (or global) scope? If it is defined only in ZPT, I believe the links cannot be "seen" because the other project is out of scope for the rule. To solve this, move the rule /…

Please try adjusting to this, without the lookup issues action (if you need the custom fields) * trigger: scheduled with no JQL * action: Send Web Request, to get the data with the REST API call and JQL * condition: check the response of the request was successful * action: send email, using the {{webhookResponse}} data to…

Hi @Tom Scoggin Looking at what you have posted, I wonder: are you doing this in an Automation for Jira rule or by some other automation mechanism? And, are you using Jira Cloud, not the Server or Data Center versions? If so, I recall a conversation with Atlassian Support from a couple of years ago that the {{issues}}…

Thanks for that information! I see two possible causes of this symptom... First, the rule is trying to add issues with Create Issue of the sub-task type in other projects. That is not possible: subtasks can only be in the same parent issue's project because they are really just part of the parent. Next, time tracking…

You have most of what you need in your current rule, so perhaps disable that one and copy it as a start. Next, you need to decide which epics you want to update: all of them in the project, only ones not "done", etc. For that, write a JQL statement which returns those epics. Now the rule changes... * trigger: scheduled,…

Hi @Maria Lopez Alurralde Yes, and the how-to depends upon how frequently you need to do this, how many epics you have, etc. Need this one time: * export all of your issues to a spreadsheet, and perform the check there using spreadsheet functions / matching Need this often, and do not have JQL extensions: * using…

No worries; we are all learning all of the time! Without re-reading all of the prior thread posts, I'll ask: who (or what) is creating the subtask? When a person creates an issue, that rule will certainly trigger. If it is not, that needs to be investigated further. But when another rule creates an issue, by default rules…

Would you please post an image with your complete rule and of the audit log details showing the rule execution? Until we see that... I suspect your rule is trying to branch over the issues, rather than using the webhook response as a set of issues for the email.

Hi @Vivek Challa You have posted multiple questions like this recently, asking the community to just write a rule for your needs, with no apparent attempt on your part to learn about rules or solve the problem yourself. Please note this is a community of people with similar interests and offering to help each other. It is…

Hi @Vivek Challa What have you tried thus far to solve this problem? If you have created rules and are running into challenges, 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…