Bill Sheboy Expert

Hi @Sandra Vaesen -- Welcome to the Atlassian Community! First thing, a couple of questions: * What problem are you trying to solve by copying the comment? i.e. is this for reporting? * What do you want to do when the flag is removed? e.g. clear the field, store the comment added when clearing the flag, something else?…

I am glad to learn you have a rule that works for you. As you note, JQL with smart values cannot be validated when creating the rule...And that is why you could test manually with Advanced Issue Search first (or by typing in a value as you have done), and then substituting in the smart value. Regarding your next goal,…

Hi @Dom With an automation rule, you cannot nest branches/loops currently. What you can do is divide and conquer to solve the problem with 2 rules: * use your rule, up to the point and including the first loop, and add a value/comment/etc. to delegate to those issues * create a second rule, triggered on the condition from…

Hi @Allen Trevethan Just a heads up for your use case: if you are triggering the rule on Sprint Started and then adding issues to the sprint, that will show up as scope change for your sprints. An alternative would be to trigger on Sprint Created so the issues are assigned to the sprint at the time of sprint start, causing…

Hi @Sambath SUN Yes, and...to what Mykenna suggests: For company-managed projects, the "Epic Name" field still exists and for team-managed projects only the "Summary" is used for epics. My understanding is this is changing, as the "Epic Name" field is being sunset over time, and so only "Summary" will be used. Kind…

Hi @Chris Smith -- Welcome to the Atlassian Community! You may not need to loop through these; instead only find an example issue with the "highest" priority. For example, try writing some JQL which will find all the relevant issues you want, and then add an ORDER BY Priority ASC Now the last one should have your target…

Hi @Janosik, Juraj -- Welcome to the Atlassian Community! Please take a look at these sources for Atlassian information on plan levels and specifics about automation service limits: https://support.atlassian.com/jira-cloud-administration/docs/explore-jira-cloud-plans/…

Hi @Els Vercauteren First thing, remember that JQL is not a SQL, and so things that may be obvious to do in a SQL do not apply. You may be observing this behavior because the hyphen is the exclude token for JQL: https://support.atlassian.com/jira-software-cloud/docs/search-syntax-for-text-fields/ Perhaps try escaping that…

Hi @Mariam Hovhannisyan I believe that with out-of-the-box features, only the site admin can see that information on the audit log. https://support.atlassian.com/jira-cloud-administration/docs/audit-activities-in-jira-applications/ Without site admin permissions, I believe you could create automation rules to track such…

Hi @Hermance NDounga Thanks for openly sharing this information! You seem to describe that Jira Product Discovery (JPD) projects are instances of Team-managed projects (TMP). When this suggestion to share custom fields between TMP projects is implemented, will that automagically apply for JPD also?…

No, I cannot; I have not tried that with an automation rule yet.

Correct that you need to reference the specific field to use the matching functions.

Excellent! I am glad that was it, as I was running out of suggestions. :^)

Does your trigger have any JQL, as that could cause duplication? And as you are referencing other assignee fields in the email (e.g. displayName) I do not think you can just use the accountId to drive the loop/advanced branch. I just tried this rule logic like yours and it worked for me: * trigger: scheduled with no JQL *…

Thanks for the additional details, and with the example rule I provided you should be able to create the rule, with these adjustments: * adjust the JQL for the schedule trigger to check for status value not changed in the last 2 hours * and then use a couple of conditions to check for "no comments" or "last comment added >…

Thanks for clarifying! You mean you have 30+ "Jira Components" not "rule components", correct? If so, you may be able to use an advanced branch over smart values to iterate over the Jira Components in the trigger issue. This would make your rule significantly smaller, and most likely would not need a test for each…

First thing, you may want to try this free training from Atlassian on using JQL to answer questions. https://university.atlassian.com/student/path/849533-gain-project-insights-through-jql Lots of our non-development background people find it helpful. Next, you may not need JQL extensions/addons for your rule, so let's…

Hi @SHEHZADALI ISMAILY This is a common use case, and there is a comparable example in the Automation Template Library: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/140671 You may review that rule, which uses parents and subtasks, and change your rule to check linked issues instead.…

Thanks for those details and your summary. Perhaps this rule would implement your idea of waiting until the "Move to Preview" issue is created: * trigger: issue created * action: re-fetch (this will slow down the rule and reload the data, preventing timing problems from the trigger firing too quickly) * condition: ???…

What I provided was an example of the structure. You will need to look at all possible combinations to decide what your want the outcome to be, and adjust the rule accordingly, reducing the similar cases. Off the top of my head, here are some scenarios to decide if a label should/should not be added. Assumption: the issue…

I suggest creating a rule to try this and experiment toward what you need, writing information to the audit log for your analysis and checking. This is your use case, and others may not come up with the exact steps to match your need. For you next steps, please identify some example issues which have checklist items you…

Hi @Janakiraman S I recall automation rules are supported for that vendor's checklist product by accessing their custom fields. What have you tried thus far that is not working? Perhaps if you post images of your rule and the audit log details showing the execution, and describe the symptoms, the community can offer…

Hi @Parsa Mounika Adding to Max's answer: One free addon you could try is the Automation for Jira (Lite version). Here is an example rule doing what you describe: https://www.atlassian.com/software/jira/automation-template-library/rules#/rule/112180 Kind regards, Bill

There is no OR clause or condition structure in automation rules at this time. A work-around would be to use a less restrictive JQL for the trigger, and then test both conditions using if/else structures, such as: * trigger: scheduled every 2 hours, with JQL* project = myProjectName AND statusCategory != Done * if/else…

If I understand the technique you tried...Incrementing a loop counter inside of a branch (which could process more than one issue) does not work in a predictable manner. Such branches split off to execute independently and asynchronously, and so the variable is created new for each pass of the loop. The only branches which…

Hi @Kumar Time-based assignment rotation is not one of the built-in options: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Assign-issue You could probably build this by performing math on the current week number with some if/else conditions, however... What have you considered for the impacts…

Hi @Akhil Mishra There are a couple of open suggestions to help with this use case, such as adding "copy components" and adding OR condition handling: * https://codebarrel.atlassian.net/browse/AUT-781 * https://codebarrel.atlassian.net/browse/AUT-2036 For your question, what do you mean by "...so that i can just simply…

Thanks! That one is a troubling and curious behavior. Lots of people, including me, rely on the audit log for tracking rule behavior...and seeing this is gonna make me check my rules more closely.

Even though it will be a maintenance problem, you may want to consider multiple rules...where each one handles one-and-only-one environment. Also consider working with your site admin to contact Atlassian Support to learn if they have other suggestions.

Please try writing that value to the audit log to see what appears... * If the value is blank/absent in the audit log...* the lookup is empty (e.g. JQL problem) or * the source issues have no story point values * If the value is present, something else is preventing the field update