Bill Sheboy Expert

Hi @KristinaH There is nothing built-in that does that for Jira Cloud, so you have either a marketplace addon or an app your company built/added. As you appear to be a site admin, I recommend using the top-navigation bar to look at: Apps > Manager your apps From there you should find that application, and the be able to…

Thanks for clarifying. When you used that how-to article to find your field's smart value, did you find it? That is, for your example issue you tried did you see a smart value and custom field id for it?

My understanding is many of the fields in Advanced Roadmaps are not supported by APIs that automation rules use. I am glad to learn you have all the fields working now. Do you consider this one solved?

You are missing 2 calls to Re-fetch Issue... Add one immediately after the trigger, and before the condition test Add another after the first edit issue action. So the rule will look like this: * trigger... * action: Re-fetch issue * condition... * action: edit issue for Epic Link, Fix Versions, Labels, and Classification…

Hi @Angelica Machado I do not believe that is possible with the built-in JQL. Your date range for the test is using worklog, which is for time keeping. And the comment dates cannot be queried. A possible work-around is to investigate the Atlassian Marketplace for addons to JQL which add this capability. Kind regards, Bill

Hi @sacha_rouzkhosh Smart values are name, spacing, and case-sensitive. And, the documentation does not list them all. Please try this how-to article to learn the smart values you need for that expression: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/ Next, I note you want to…

Hi @Jamie Edmondson First thing, not all supported fields are listed in the automation rule, drop-down lists. To learn if your field is supported, and to learn its exact smart value, please use this how-to article. Essentially you identify an example issue with your field, call a REST API function with a browser, and…

Hi @Jeff Cumbie -- Welcome to the Atlassian Community! When do you need to complete this and what version of Jira Server, automation are you using? I ask, because the lookup issues action just got added for server, and that would make doing this much easier as you could use JQL to gather the issues and then use min and max…

Hi @Sam Hepworth -- Welcome to the Atlassian Community! I did a quick check of the editmeta data and it does not show "remove" as a supported operation for issue links, for the REST API functions available to rules. So, a noisy work-around (noisy because it causes several issue changes in the history): * capture your…

Hi @Raj Vora That result sounds correct to me: no issues returned. When an issue type is created, using it (or not) is a configuration choice due to the dynamic nature of the Jira solution. And so if you use JQL to search, it will be present or not. However when you try to search for a non-existent issue type, that…

Hi @Ashwini Yerabati Would you please post an image of your complete rule, including details of what you have tried thus far to solve this? That context will help the community offer ideas. Thanks! Until we see that...Your scenario might be possible, and it depends on a few things: * How likely is it your summary will have…

Would you please post an image of your current, complete rule...including details of the action to set the team? Thanks!

Hi @Cindy I do not believe that is possible with JQL. You could instead create an automation rule, triggered on issue create, which checks the link type to inform you. To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @Pooja Sree When you want a cloned issue to have the same status as the source issue (although I am unclear of your use case for that) it usually happens immediately after the cloning. So, where does the cloning happen: * if you clone the issue from inside of a rule, the status can be set * if you clone manually (i.e.,…

There is a rule action named Re-fetch Issue: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html

Hi @Dhanyasri When do you need to implement this, and what version of Jira Server, automation are you using? I ask because the Lookup Issues action was just completed and is rolling out for Jira Server: https://jira.atlassian.com/browse/JIRAAUTOSERVER-53 With Lookup Issues, and smart value list filtering, this scenario…

That is curious...I wonder how that manifests in the rule execution differently for ones created by Issue Collector. There is a known behavior that the Issue Created trigger can occur so quickly that other data is not available for the rule to use it. And, subsequently your edits could be "walking over" each other and…

Hi @Jacob Where are you trying to perform this test: in an automation rule, somewhere else? If in an automation rule, you could probably do this test with either an advanced compare condition or with a regular expression and a match() function. Kind regards, Bill

Hi @george_bullock I believe mean in that context is the "arithmetic mean", which is the average. And that is indeed influenced by outlier values. If instead you meant the median, there is nothing built-in which can show that value. If you are seeing these resolution time values on the built-in, Atlassian interpretation of…

Hi @Arild Hoyland -- Welcome to the Atlassian Community! First thing, context is important for automation rules. For a question like this, please consider also posting images of the complete rule and audit log details showing the rule execution. That can help see where the symptom is appearing in the rule execution.…

Yes, that helps; thanks! When you edit an issue in a rule, particularly the trigger issue, it is using the current conditions at the time the rule was triggered. If you want to include the latest edits, each edit must be followed by the Re-fetch Issue action to reload the information before the rule proceeds. Because each…

Hmmm...I wonder if there is a different issue related to your rule structure. Would you please post an image of your entire rule, and include an image of the edit issue action?

Let's test that hypothesis... Before your branch, write this to the audit log, run the rule, and then observe the results to compare the number of comments found to what you expected: Number of comments found: {{destinationIssue.comments.size|0}}

I think the error could be caused by one of two things: a trailing comma or the incorrect syntax. Please try one of these: { "fields": { "customfield_10101": "1080" } } Or... { "fields": { "customfield_10101": { "id" : 1080 } } }

Thanks for clarifying, Pablo. What you are trying to measure is often called "Time In Status" and can sum up to "Build Cycle Time" when it spans the different status values from start-of-work until completion. There is nothing built-in which can do that for working hours. Instead the built-in, Atlassian interpretation of…

Unless you can branch to the issues, it may not be possible. To save you time, there is no REST API function to log work for another user, and so if the issues are assigned to another person this would not work. What information are you using to log work: amount, date/time, etc.? It might be possible to divide and conquer…

First thing, using automation rules requires learning and experimentation. I recommend trying to create your rule(s) to help you learn about this. I wonder what you mean by "as soon as there are less than 4 tickets in the backlog for an employee". That could mean a few things: * when an issue is completed, check the…

As you wanted to do this for epics, I was suggesting to perform the issue type test first, and then the others. For example: * trigger... * condition: issue type is Epic * if/else condition for epic name equals Initialize* assign as needed * else/if condition for epic name equals Hardware* assign as needed * and so forth...

Hi @Dave Brennan Adding to Mikael's answer... "Advanced issue search" was renamed to "View All Issues" in some places (and just "JQL" in others), and so suggested tips may have been missed in some application info. You may also find the search from the top navigation bar: Filters > View All Issues Kind regards, Bill

Hi @Isabella Musial As Jira has several things named "Team" I recommend using the custom field id in that JSON expression. You may find the correct value using the how-to article linked below. Essentially you identify an example issue with your field, call a REST API function to see all supported fields, and then search on…