Bill Sheboy Expert

Hi @Noah Horton -- Welcome to the Atlassian Community! There is a known symptom where the Create Issue trigger can fire before all of the field data is available for use in the rule. One work-around is to add a Re-fetch Action immediately after your trigger. This will reload the data and slow the rule down a bit. If that…

Hi @Utku Demir -- Welcome to the Atlassian Community! When you commit from some tool outside of Jira, it does not have the same user information, and so the {{initiator}} cannot be a Jira User. There are open suggestions to improve the DevOps triggers to pass more information, such as the commit's…

Hi @Hussain Bin Ali -- Welcome to the Atlassian Community! One possible way to do this is with an automation rule and a custom field to store the developer. * add a custom field, such as Assigned Developer * create an automation rule which saves the Assigned Developer when an issue is in your "development" status * create…

Yes, and...to the excellent ideas provided thus far: - for actual Projects (defined goal/scope/desired timeframe/etc.), assign people one Project at a time, helping them feel supported for success and focused on the desired outcomes - help team design/create a t-shirt, or other team identity object, for a shared visible…

Hi @Heidi Smith -- Welcome to the Atlassian Community! To confirm your use case, do you want the count to be the current count at all times, handling cases of both add/remove links? If so, perhaps instead structure the rule triggered and checked for only the non-bug types, so it always recounts the linked bugs, with JQL…

Hi, @Doug Levitt First thing: wow, that surprises me it takes that long! I would submit a defect for that one to Atlassian. Is this a global/multi-project or a project-scope rule? As for a work-around, there is no available smart value/action to set a user field to the Project Lead yet. But you could disable the automatic…

Hi @Dmitry Alabyan Would you please post images of your current rule and the audit log details? That may provide context for the community to offer suggestions. Thanks! Until then, I am not familiar with a branch type of "for every project". Are you using Jira Cloud, Jira Data Center/Server, or some other Atlassian…

Hi @Sreenatha Reddy J Would you please post images of the rule, including the trigger details, and of the audit log? Those may provide context for the community to offer suggestions. Thanks! Until then, you note that: I have Given like Project in(Project1, Project2, Project3) and once I click on validate it is not…

Hi @Doug Levitt I recall another post about this months ago, and the person noted they could do this by creating the condition outside of the if/else and then dragging it inside with the rule editor. I just tried this and it still works...However... As the rule editor does not offer adding the condition this way natively,…

Hi @HariVLK Mynampati -- Welcome to the Atlassian Community! As @Fabian Lim noted, this is not possible with out-of-the-box JQL, so you would need a marketplace addon for JQL or reporting to do this. For work-arounds without purchasing a marketplace addon, how often do you need this? * Just one time: create a JQL filter…

Hi @Yash Raj Please post images of your rule, and the audit log details when you have a question, including what is not working as you expect. That will provide context for the community to offer suggestions. Thanks! For example, what is different for subtracting the other field using the same methods you have already…

Hi, Martin. Writing automation rules often requires experimentation. I encourage you to try things, such as writing comments to the audit log, to learn more about how Jira implements things like mentions...as that will give you ideas for how to parse them with regular expressions. To get you started, this expression will…

I wonder if that time value is text (because of possible units of measure). Perhaps try adding .asNumber.sum to convert before summation. Also, smart values are case-sensitive, and I note you made that one all lower case. Perhaps try making it match your first variable and the…

Yes, that error matches what I noted earlier. Please add this to your branch JQL to exclude the trigger issue: AND key != {{triggerIssue.key}}

Hi @[deleted] First thing, I find putting story points at the sub-task level seems both different than the intent of using sub-tasks (i.e. non-releasable child items which contribute to building a releasable thing, such as a story) and to create busy work to gather the measures later for team use. With that out of the…

Hi @Abby Chang If you note the values you entered, it seems the fields are interpreting the dates in the format of yy/MMM/dd rather than dd/MMM/yy as that would cause that error message. Perhaps check your settings to see if that is the case. Kind regards, Bill

Thanks for clarifying, and good luck!

Hi @Frank Eilts First thing, I am using Jira Cloud, so what you see may be different for the Data Center/Server version of automation for Jira. With that disclaimer out of the way... When I call that REST API method I get all of the versions back. How do you know which one you want to add to Affects Versions? Could you…

Hi @Gee Udobang Yes, and...to John's answer: I believe that if the board owner set the location with their profile (rather than a project) it will also appear as "Private" in the boards list. Kind regards, Bill

Hi @Stephan Grubbe I believe you have summarized this use case well with your note "that seems rather complex and time-consuming" :^) If your team is moving an issue from one active sprint to another one, you may need to check the history to find the current/latest value. Based upon my experience with automation rules…

Hi @Martin Fukatko A couple of ways to do this are with an advanced, smart value branch to loop and with a single edit: * Loop: Use a regular expression with match() to parse the users' account ID values out of the comment, and then use that result as the input for an advanced branch. Within the branch use an advanced edit…

Jira Data Center/Server has two possible versions of Automation for Jira. Here is the comparison of the versions, paid and free, to help you confirm which one you have, and the marketplace link to confirm you are updated: https://confluence.atlassian.com/automation/getting-the-right-version-993924597.html

That's interesting. Perhaps check with your admin to check if there is an update to the automation addon. And, I guess it is also possible that only the Pro (paid) and not Lite (free) version has this feature, although I would find that surprising as it is essential to manage usage and troubleshoot misbehaving rules.

Hi @Kellie Bower -- Welcome to the Atlassian Community! Yes, you could do that with automation rules. For example if you wanted to do this when the issue is created, it would be something like this: * trigger: issue created * action: re-fetch (to reload the data) * condition: issue type is a subtask * if/else…

Hi @Houssein Barkallah You cannot do that with out-of-the-box features of Jira Cloud JQL. Some work-arounds are to check the Atlassian Marketplace for addon apps that enhance JQL or enhance reporting, or use custom fields with automation rules to track this for a specific field. Kind regards, Bill

Hi @Robert Leachman First thing, I am using Cloud and not Data Center/Server versions... The documentation for Data Center/Server does show this feature is available: https://confluence.atlassian.com/automation/view-performance-insights-for-automation-rules-1013851985.html Kind regards, Bill

Hi @Warren Turner To provide some context, would you please post images of your complete rule, details of the summation/edit components used, and of the audit log details showing the rule execution? Thanks! Kind regards, Bill

Those two fields/design choice cause quite a bit of confusion, so we are not alone on that point :^)

You do not show what is in your advanced branch as the source, and if it is lookup issues you may need to specify the keys. The other way to do this is just with a branch: * ...some rule steps * branch: on the JQL you use for your Lookup Issues (instead of using the lookup)* action: add comment, one by one for each issue…

Hi @Pankaj Gupta -- Welcome to the Atlassian Community! I do not believe that is possible with out-of-the-box JQL features. CHANGED BY user only accepts one value, and so your work-around would be to add a bunch of OR clauses, listing each user: ... AND ( CHANGED BY user1 OR CHANGED BY user2 OR... ) Or you could…