Bill Sheboy Expert

Your screen images did not post, but they may not be needed. As your field is numeric please try the rightPad() technique and let me know how that helps. Thanks!

Are the spaces embedded within the version names (and so do not match others) or leading / trailing spaces? If they are the leading / trailing ones, let's add the trim() function to also prevent potential duplicates: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#trim-- Please see my…

Hi @Asheesh What is the type of your field, UT-IssueCount? Is it a numeric field? Please show an image of your advanced branch to provide context. Until we see those... There is no built-in branch type to iterate over a numeric value. Instead you may try a couple of possible workarounds: * Use a text string to replicate…

The Epic Link, Epic Status, and Epic Name fields are being sunset, a change which started in 2023 and which continues now: https://community.atlassian.com/t5/Jira-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562 And so it is possible your issue does not contain a value for Epic Name. The…

Please post an image of your complete rule and an image of the audit log details showing the rule execution. Those may provide context to help explain what you are observing.

Hi @sridevi nimmagadda -- Welcome to the Atlassian Community! There is no built-in feature to do that. There is a suggestion to add the feature, which you may vote for to see progress: https://jira.atlassian.com/browse/JSWCLOUD-22870 As a workaround you could add Quick Filters with JQL for your component values to select…

Hi @Shivani Saran -- Welcome to the Atlassian Community! Please post images of your complete automation rule, the action where the linking occurs, and of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Thanks! Until we see those... Are the issues all in…

That is curious... This rule appears to be global scope, and the trigger issue is in the project S0C2 (note that is a zero in the key) and you are trying to link to an issue in SOC2 (note that is an O in the name). And so these issues are not in the same project. Is that correct as you mentioned earlier the issues were in…

Thanks for that information. Rather than using the Edit Issue action, please use the Link Issues action to do so. Then re-test and post updated images of your rule and the audit log details. Also I note you have changed the rule actor from Automation for Jira to your own user. Why make that change? Sometimes that change…

Hi @Jodi Jones Where did you find that description of the Contributor role for Jira Product Discovery (JPD)? Please look here to learn what the roles can / cannot do, and possible options to allow a Contributor to create…

Hi @Kristine Daniels 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 @Jodi Jones For Jira Scrum boards, an issue must be in the right-most board column to be considered completed for the sprint, and thus to impact the burndown and other reports. The status category has no impact on completeness for sprints. As you describe your issues being in at least "Ready for Release" as part of the…

That does appear to be a timing problem, and I would have expected a single Re-fetch Issue action after the trigger to have resolved this (given what the history shows). I recommend working with your Site Admin to contact Atlassian Support to learn what they suggest: https://support.atlassian.com/contact/#/ While waiting…

Thanks for those screen images. Did you look at the issue history for AR-349 to observe when the Location and other custom fields were set?

Hi @Sampath Jira Query Language (JQL) helps find / search for issues. It cannot perform calculations for things like duration of time between date fields. And it is not a SQL. Please look here to learn more: https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/ For…

Hi @Ian Robinson Regarding the types of the fields, your usage will determine which types are better fits for mapping to the JPD fields. Perhaps discuss this scenario with your JPD users to learn what is needed. For copying the fields when creating the issue (i.e., JPD idea), I recommend creating a rule and trying to copy…

Hi @Pamela Hein Without seeing the specifics of your rule or the audit log details, this symptom does seem like a delay / racetrack error. If you look at an example issue's history, when do you see the fields populated: when the issue is created or at some time later? Kind regards, Bill

Hi @Lynnette Akamine -- Welcome to the Atlassian Community! You are correct: cloning forms directly is still not supported for automation rules. Here is the suggestion to add that, including a workaround where the rule calls the REST API to copy the form: https://jira.atlassian.com/browse/JSDCLOUD-10939 Kind regards, Bill

Hi @Tasneem Abdelhameed That is not possible with the built-in features of automation rules yet. However as a workaround, your automation rule could use the Send Web Request action to call the REST API endpoint to get the approvers. If you want to try that, here is a how-to article for calling the REST API from a rule and…

Please post an image of the audit log details showing the rule execution. Does the issue have any assignee at the time rule executes? Finally, your rule appears to use the Issue Created trigger. That trigger may fire so quickly that some data issue data may not yet be available to the rule. The solution for that symptom is…

Hi @Amy Chang Yes, that is possible with a rule. Rather than branching to the Parent to access the child issues, you could instead use the Related Issues condition to check the sibling "Task" issues. If that condition passes, then branch to the "Request". * trigger: issue transitioned to Done or Closed * condition: check…

Hi @Raj, Rohit -- Welcome to the Atlassian Community! Context is important for automation rule questions. I recommend creating a new question, linking back to this thread, and in your question include the following: * what problem are you trying to solve with the rule; that is, "why do this" * an image of your complete…

Hi @Patricia Johansson This appears to be a symptom of this new defect: https://jira.atlassian.com/browse/JRACLOUD-84725 You may vote for / watch it to see progress. Kind regards, Bill

Hi, and thanks for the well-written article, @Trudy P Claspill A couple of suggested improvements could be: * add links to the relevant documentation (e.g., create variables, date / time functions, etc.) so people can learn more about how the steps work, and * add to the caveats about potential impacts for excessive…

My understanding is the Atlassian team has attempted to address this iterator limitation in the automation engine several times without success. You could also create a service external to the rule, passing your client ID to perform the lookup / filtering there and return the result to the rule.

Hi @Sebastian Brunet -- Welcome to the Atlassian Community! Context is important for many rule actions, particularly for creating subtasks. As your your trigger issue is apparently the Story, there is no need to branch. For example: * trigger: issue created * action: re-fetch issue (I recommend always adding this action…

Hi @Antonio Smith 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 ideas.…

Hi @Daniel Welch -- Welcome to the Atlassian Community! If you search this community, you will find several posts for this same question and different solution approaches. One way to do this is with automation rules; the specifics depend upon when / how accurately you want the parent updated. For example, let's assume you…

Hi @Nicolas Andika Will your trigger issue always have Fix Version values for the comparison in the JQL? If so, please try this to iterate over the values and create the list of version names: fixVersion IN ( {{#issue.fixVersions}}"{{name}}"{{^last}}, {{/}}{{/}} ) If you also need to handle the case when the trigger issue…

Hi @IL This is a known limitation of automation rule iterators: once inside the scope of the iterator, it cannot access data / smart values at any higher / other level. And so your variable specialClientId is not visible inside of the iterator {{#webResponse}} ... {{/}} Depending upon what is needed, there are a couple of…