Bill Sheboy Expert

Hi @Adil Iqbal Which user field are you trying to use for the smart values? Here is a list of the built-in field smart values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/ Are you using a custom field instead? If so, what is the smart value for your field? Once you identify the field, you…

Hi @thumuluru.shreya As @Marc -Devoteam- suggests, context is important for automation rule questions: please post the complete rule, action details, and audit log details to help the community provide suggestions. Until we see those... If the values you show are in fact the values of the custom fields, you could use: *…

Hi @Shashank Is this question for an automation rule? If so, context is important for the community to help with automation questions. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions /…

Hi @Steve Teiv -- Welcome to the Atlassian Community! For Jira Data Center, the Lookup Issues action does not support custom fields yet. As you want to set another field based upon the values in the child issues of the Epic, the REST API will need to be used. Please see this post I made in another question for more…

Hi @Santhiswaroop.a You already asked this exact same question yesterday and there were a couple of responses: https://community.atlassian.com/t5/Jira-questions/Automation/qaq-p/2905790 Please stay with that one to focus the conversation. Kind regards, Bill

Hi @Eric Roetenberg To which project are you trying to refer in those Issue Create actions to set the summary field: the destination project where the issue is being added, or something else? If it is to the destination project, what you show will not work. The issue has not been created yet and so the smart value…

Hi @Edgar Pusklevic Yes, that is possible with a multiple-project scope rule. Your Jira Site Admin will need to help set that up. And the key is how do you relate the issues for finding them: an issue link, etc. The rule could test in which project the trigger issue had a comment added and then use an if / else block to…

Hi @Trudy P Claspill and @James Schnur It appears that suggestion JRACLOUD-74498 was moved to the JPD project (i.e., JPD-245) and that one is only visible to the internal, Atlassian team. Searching the visible, public backlogs, I did not find any open suggestions, although I found this one closed as "won't do": Include the…

Please note well: chained rules like this can be difficult to build, so I recommend testing thoroughly before performing any actions that cannot be reversed. For example, you could change the first rule trigger to manual and replace actions (such as Send Web Request) with writes to the audit log until you have confirmed…

Hi @Óscar Mestre Adding to the suggestion from @Fazila Ashraf ... With the Issue Created trigger, that can fire so quickly that the issue data may not yet be available to the rule, leading to potential problems. This is particularly the case when one rule's actions trigger another. To help mitigate this, I recommend always…

Hi @Santhiswaroop.a -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have an automation rule that is not working as expected, context is important for the community to offer help. Please post the following: * what problem are you trying to solve; that is, "why do this" * what…

Hi @Dirk Aerts JPD recently added some features for issue hierarchies; please see this article to learn more: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/A-giant-update-for-hierarchies-issue-types-opportunity-solution/ba-p/2893631 As @Rudy Holtkamp describes, automation branches which could be on…

Hi @Gilad Waldman Short answer: the only ways I know to do this with the REST API or an automation rule is divide-and-conquer, such as sum first at the Epic level and then sum the Epics. You could also build your own app to page through repeated calls to the REST API endpoints. More information... The 100 issue limit is…

Hi @Yaniv Ben-Dror -- Welcome to the Atlassian Community! Adding to the suggestions from @Tomislav Tobijas ... That smart values "help" feature is quite new, and my understanding is it will eventually load all possible smart values and not just a static list. While we wait for that, you may learn the available smart values…

Hi @Sebastian Morton -- Welcome to the Atlassian Community! When a variable is created within a branch, it normally only exists within that branch as that is its "scope". And so when you do this will multiple branches the values are not visible outside the branches. There are a two things to try to solve your percentage…

Hi @Michael Landry Thanks for this information, and I just replicated this symptom so this appears to be a defect where: * at this time, the Fix Versions cannot be set from the dropdown field in the Issue Create action, and... * immediately after the issue is created, the Fix Versions cannot be set using the Edit Issue…

Hi, @Valerie Knapp and that list looks familiar to me ;^) I will remove my post so we can help focus the conversation. Kind regards, Bill

Updated: removing my list of questions to help focus the discussion.

Thanks for that information, @SAzaruddin.mp If this was a team-managed project, this symptom would be explainable (as the types are different for each project) but not for company-managed projects. At this point, I recommend working with your Jira Site Admin to ask the Atlassian Support Team to take a…

Hi @Jack Brickey A couple of years ago, customers lost access to the internal, old Codebarrel backlog and blogs. That suggestion to add a rule action for Archive Issue got copied to the new backlog here: https://jira.atlassian.com/browse/AUTO-1562 Hi Ari, Here is a how-to article for calling a REST API endpoint from a rule…

Hi @Eran Roiter There are challenges when rules with the Issue Deleted trigger try to access any related issues: * things like branch to parent no longer work as the connection may already be removed * same challenge for branching to linked issues * using a JQL branch will not work because behind the scenes, rules…

The three calls I was noting were to add enough delay and confirm the presence of the page before proceeding. These were still all in one rule. * create the page * get the content for the page just created * update the page content

Hi @Donni Shimanovich -- Welcome to the Atlassian Community! There is a known, racetrack error with the Issue Created trigger. That is, the trigger can fire so quickly some issue data is not available to the rule yet. This often leads to missing data and unusual rule errors. I wonder if what you are observing is a case of…

Thanks for performing that test, as it indicates the rule is comparing to some other type of "Epic". Please also answer the three earlier questions asked: * What type of project is this: company-managed or team-managed? That may be found at the bottom-left side of the page or in the project list. * What is the scope of the…

Hi @Shahid Meman -- Welcome to the Atlassian Community! From the rule you show, you are using the Lookup Issues action with JQL to gather issues to get some issue count measures for a Slack message. And, you want to add a hyperlink to the issues for each measure. If your JQL for the rule are static / stable, you could save…

For the going backwards in flow, I am unclear how a rule could do that without first storing the values somewhere, such as in additional custom fields or entity properties. Looking at what you show for the comment, that is probably adding the users as their accountId values, correct? If you want them as their displayName…

Hi @Matthew Chavan -- Welcome to the Atlassian Community! For a question like this, please also post an image of the audit log details showing the rule execution. And...it can help to use a screen capture tool or browser addon with scrolling page support for longer rule images. Please use one of those to post an image of…

Based on what the audit log shows, the rule is not detecting that issue is an "Epic". To narrow down the cause... Let's start with the simplest possible cause: a "broken" rule. Rules which have been edited and published too many times can get "glitched", showing odd symptoms / errors. The way to check this is: * disable…

Awesome; I am glad to learn that helped!

My understanding is the new endpoint to "Delete and Replace Version" automagically finds and updates the issues and so no branching over issues is needed. Instead identify each minor version to replace and use that in the call with branching. To do that, the rule could use JQL to find the issues and load them with the…