Bill Sheboy Expert

While that is possible with an automation rule, it seems problematic for several reasons: First, it is going from the lowest issue item --> upwards to gather and display the Idea status, which seems the opposite of what many would use to assess progress. What problem are you trying to solve by showing the Idea status in…

As written, your rule is creating issues and linking them in two different operations. Did you try linking the issue when it was created, rather than linking afterwards? What are the types of product and project for each project involved: * product: Jira, JSM, etc. * project: Work Management, Software, JPD, etc. * type:…

I am glad to learn that helped! For your bonus question... Rules have scope: single-project, multiple-project, and global: * Single-project scope rules can create (or clone) issues into other projects, but not access them in any other way. That is, their fields cannot be "seen" nor edited. * Multiple-project and global…

Just to confirm, did that solve the question? If so, please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

I believe the distinct list function works with all of the Jira versions. Let's pause to get some context to see how that helps... Please post the following: * what version of Jira are you using Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, etc. * an image of your…

Hi @Mireya Cintora You may select the Reporter field in the Create Issue action (recently renamed to Create Work Item). When you do that, type {{initiator.accountId}} in the field, and when it appears below the field, select it for use. Kind regards, Bill

Hi @Salvatore Conte -- Welcome to the Atlassian Community! When only creating one child Story for each new Epic created in the rule, you could set the parent with the {{createdIssue}} issue smart value; that refers to the most recent one: * action: create issue (for the new Epic) * action: create issue (for the…

Hi @Stefan Draber My hypotheses of the possible causes are timing or typing-related: * The branch is over asset data, and perhaps there is some latency in the just-in-time data look-up which does not provide the information fast enough for the split() to use * The data supplied by the branch is not text, preventing the…

Hi @Beauvois Sebastien -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity, * images of any relevant actions / conditions / branches, * an image of the audit…

Hi @Vishal Biyani The toDate function only needs the help of a specific format expression when the date or date / time is in an ambiguous or non-standard format: https://support.atlassian.com/cloud-automation/docs/examples-of-using-smart-values-with-dates/#Converting-text-to-dates Otherwise, it will will succeed with…

Hi @Adrian Avalos What you describe is not possible with out-of-the-box features of JQL. When you regularly need such types of queries, please investigate Atlassian Marketplace addons to JQL which support such nested querying. Kind regards, Bill

Hi @Sean Kendall -- Welcome to the Atlassian Community! Please see this article explaining rules for scenarios like this: https://confluence.atlassian.com/jirakb/automation-to-send-email-only-once-per-assignee-1310985609.html The key concepts are: * the scheduled trigger has no JQL * the first lookup identifies the issues…

Hi @Morara -- Welcome to the Atlassian Community! Based on what you describe, if you are using only company-managed projects, selecting the project ID from a field will work with a single issue type such as Task. The problem is the Create Issue action cannot validate the issue type if company-managed or team-managed…

Yup, "great power, great responsibility..." leading to "oops...umm, can someone fix that for me..." for all things TMP-like :^) At my last company, we used training, documentation, and delegation to help a bit: * only two of the Creators were also admins for the JPD project * the site admins partnered to inform / train…

Hi @Hais_ Pedro I do not believe the list conditionals and blocks can be merged that way. A workaround might be to first filter on internal, saving the results in a variable with a delimiter; split() with the delimiter back into a list and grab the last entry: * action: create variable* name: varNonInternalComments *…

Hi @Mathew Lederman In my opinion, it is somewhere in the middle of what you ask... Jira Product Discovery (JPD) appears to be based upon team-managed projects (TMP), and so the fields, configuration, licensing, etc. are independent of other company-managed projects. However, some of the limitations in JPD (as with TMP)…

Hi @Juraj -- Welcome to the Atlassian Community! Without seeing the specifics of your issue Description's format, this is might be possible by: * using text functions to extract the parent key * branching to the parent with JQL * testing if the issue type supports having subtasks with a condition * adding the subtask…

Thanks for that information, and there are multiple causes for that symptom. Seeing the complete rule and audit log details for the rule executions (as @Marc -Devoteam- requested) may help to confirm these. For example... Perhaps the REST API call does not return a value for one-or-more of the email addresses, leading to…

Hi @Holly Hammond -- Welcome to the Atlassian Community! Short answer: although it might be possible to merge those rules, I recommend against some of what you describe. What problem you are are to solve by merging the rules? That is, "why do this?" Knowing that may help the community to offer other suggestions. Until we…

Due Date is one of the pesky built-in fields that has multiple smart values. Please try this one in your expression: {{issue.duedate}}

Interesting... Was your Jira Cloud site converted from a Server or Data Center site?

Hi @Charles Brooks -- Welcome to the Atlassian Community! If there are multiple fields with the same name causing confusion (which is a different problem), you can identify the needed one using this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ The essential steps are…

Hi @Tiago Ervatti -- Welcome to the Atlassian Community! Are you describing a single web response could contain multiple accountId values, or something else? If the web response could contain multiple values, you could iterate over them in the dynamically created JSON expression to add them. If instead there are multiple…

Hi @Renata Klimiato -- Welcome to the Atlassian Community! Although there are timing / racetrack processing concerns in automation rules, I recommend only introducing intentional delays when necessary. Let's look at the specifics of your rule to understand those... The Issue Created trigger often fires before an issue is…

Hi @binh_pham I hypothesize what you are observing is likely the intended behavior because... * Jira Product Discovery (JPD) has Ideas, such as representing the portfolio of things to implement * For each Idea, zero-to-many "Delivery Tickets" may be associated, using the linking type specific to JPD * And those delivery…

Hi @Aliaksandr Ropat -- Welcome to the Atlassian Community! Jira Product Discovery (JPD) seems to be based on team-managed projects (JPD), and "people" fields in those do not provide the email address to rules. Here is the "suggestion" to fix that defect: https://jira.atlassian.com/browse/AUTO-519 Unfortunately, the…

I am glad to learn the rule is working for you! Regarding my other suggestions... Once the rule is inside that first if / else block, the branch on current issue is not needed because the rule is already acting on the current issue. The conditions on Area Crew and related issues will work without it. The key is being…

If you mention that user directly when creating a comment manually, what do you see: their display name or "unknown"?

Hi @Nicole Gosling I would expect the updated rule you show with the If / Else block to work for this scenario, although the branch on current issue is not needed...and neither is the condition on the Else: you could just assume the field is empty. Without changing anything, would you please post an image showing the audit…

Hi @Gemma Joye Libed -- Welcome to the Atlassian Community! 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 in a single image for continuity * images of…