Bill Sheboy Expert

Hi @Nikola Gaydarov Posting some thoughts after your ping from the other thread...Note I am using Jira Cloud, not Data Center/Server, so please verify my suggestions in your environment. Unfortunately, I do not believe the feature to help looping is supported with Data Center/Server yet: advanced branching on smart values.…

Thanks for clarifying! I would recommend a single rule, on a scheduled trigger running every X-hours. Then use JQL to find any status changes (or lack thereof) and rule conditions to check for the last comment. Here is an example below, which you should adjust and test the JQL separately to meet your needs. * trigger:…

That last part makes sense to me: my understanding is advanced branching preserves an object (i.e. all fields of the user) while created variables are just text (i.e. and so defaulting to just accountId). The curious part is that the second distinct in the advanced branch appears to be getting confused/corrupted when spun…

Hi @Amit Gandhi I suspect that theoretically you could do that with an automation rule (with the REST API, or with multiple rules and custom fields), however... That sounds like a brittle solution: depending on the date/time difference between two unrelated events. Particularly because you have no control over what happens…

Hi @Dave F First, given the potential for spamming, I recommend modifying your data or initial JQL (or use a test project with less data) to carefully set up your testing conditions for this type of rule. That will help you limit the emails to precisely understand what is happening during testing. Next, what are you able…

Hi @Triet Bui Minh First thing, I echo the question from @Jack Brickey : what problem are you trying to solve by having both the label and the fixVersion reflect the same information? Next, when using search/replace, regular expressions, and lists in automation rules...the audit log is your friend. Try writing the…

Hi @Nadia If a person can view a board I cannot think of a reason why they could not mark it as favorite (through permissions). Perhaps you could check if this is a browser caching issue: clearing all cache, closing browser, and re-opening the browser. Kind regards, Bill

Writing automation rules is a lot about experimentation and learning (e.g. reading documentation and reading posts), and I respectfully suggestion trying both. To help you get started, here are some draft steps I suggested earlier: * trigger: issue created * action: re-fetch (This helps prevent timing errors after the…

HI @Dave Ung -- Welcome to the Atlassian Community! Agreed, and...In my experience, this is a case-by-case issue. Re-fetch usually helps with triggers and may not with misbehaving REST API calls. I recall seeing some open suggestions to solve the racetrack errors with triggers and to add an explicit "wait for <X> to happen…

Thanks for the reminder, Stefan! Indeed the order of versions in the releases/versions list is what Jira uses as "next" and "earliest". That seems to have been a design work-around as the release date fields are not required. :^)

Okay, I reproduced the symptom you are seeing: comments are not always added, although the link deleting seems to work consistently for me in a free Jira instance. I would suggest submitting this one to Atlassian Support ( https://support.atlassian.com/contact/#/ ) but it appears you are on a free license and so cannot do…

Hi @Jeremiah Would you please post an image of your automation rule? That may provide some context for this symptom. Until that is shown, I suspect what is happening is when you perform the link delete and then add more links, the trigger issue's data at the time of rule start is being used later. For example: * trigger:…

Hi @Amy Chan Please take a look at this documentation for examples of add versus update with JSON, and of how to modify the fixVersion field: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/ Kind regards, Bill

When using {{fieldChange.toString}} you are getting a text (string) version of the current field default values (e.g. cascading field id). As you appear to want the current value, that second link shows the field's smart values you may use instead in the JQL.

Hi @Meghanand Baraskar As you are trying to use JQL on the values, I believe you will need to separate the parent and child values to use cascadeOption(): https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-cascadeOptioncascadeOption-- Please…

Hi @Lynn Hagan -- Welcome to the Atlassian Community! Short answer: that is not possible with out-of-the-box features. The built-in hierarchy of issue types is Epic > Issue (story/task/bug) > Sub-task. When showing swim lanes "by story" only child subtasks could be shown in the lanes, plus the "other" lane for the…

Hi @[deleted] The answers to your questions are: yes, yes, and yes; those are possible with automation rules. The details depend upon whether or not your releases (i.e. versions) *always* have issues assigned. For example with scenarios # 1 or 2, you could use a scheduled rule (without JQL) and an action of Lookup Issues…

Hi @Shrinidhi Selvakumar -- Welcome to the Atlassian Community! If I understand your question correctly, the answer is: yes, it is possible to set a parent's field when a child issue is created. Please try using a Branch to the Parent in order to access its fields. Kind regards, Bill

Thanks for that information, Kathryn. Have you considered creating the first developer task at the same time as the initial story, in the same rule? Next, from where do you create additional developer tasks? For example, do you run the manual rule from the same initial story for the web page requirement?

Hi @Nikola Gaydarov -- Welcome to the Atlassian Community! I have not tried that, and... You could probably use match() with a regular expression to expand the other values into a new list/string, and then reform the list, either directly or with join(). You could also try using smart value list filtering to create a new…

Hi @Jean-Emmanuel BANQUEY and @Vaishali Patil I can confirm that Magic Estimation works for Ideas, although you can only "size" one attribute per session (e.g. Effort). In this case, the built-in Economic Prioritization for Jira Product Discovery may be better to allow setting both Effort and Value at once on the 2x2 grid.…

Hi! Would you please post your images of your rule and the audit log details here in this community thread. That will provide context and ensure the images are preserved for future people looking at this question. Thanks!

Hi @Morgan DUBUISSON Are you asking a different question, or are you working with Heidi on their question, or something else? Thanks, Bill

Hi @Ryan Danowski -- Welcome to the Atlassian Community! That is an interesting behavior...it seems to indicate the advanced branch variable is using object data to decide to anonymize it, or that something else in the web request action is doing so, or...? First thing, I would partner with your site admin to submit a…

Hi! I recommend pausing to talk to your Jira Admin person, as they can help you know what version of tool and project you are using. Then the community can help you update the automation rule further. Thanks!

Hi @Ryan Van Zyl -- Welcome to the Atlassian Community! First thing: lists To make a list, you supply the values with some delimiter, such as comma. That will still be a text string. Then when you need it as an actual list, you can use the split() function for use as needed. For example... * Create a variable* Name:…

Hi @Rahul Jith Starting with the JQL you are showing, please note queries evaluate AND before OR, causing some problems when you do not order your clauses or use parentheses to get what you want. I encourage you to take this free training from Atlassian on tips/techniques to writing JQL queries to learn…

I was suggestion if you are using a team-managed project to change the values, however it appears you are not. Smart values are case-sensitive, so check if this is the problem by updating the edit to this: {{lookupIssues.Story points.sum|0}}

Hi @Adrian Chavez -- Welcome to the Atlassian Community! To confirm the image you posted, is that your board view for a company-managed project? If so, those assignee avatars are for filtering the board, and I believe they only show for the people who currently have assigned issues, the current user, and "unassigned".…

Hi @Kathryn Swearingen Lots of moving parts in your solution...please consider: what would be the triggering event/conditions to form that issue link for the future issues (i.e. tickets)? As you have already created other automation rules to help, if you can identify the trigger and conditions for your workflow you can…