Bill Sheboy Expert

Hi @Tanguy Crusson Question on the select-option field, highlight (color bar) technique: It appears that once a field is added to the project with highlighting options, the highlighting appears on *all views* even when the field is not included in the view. Is that expected? I can think of scenarios where the highlighting…

Hi, Robert. After testing I learned that the match() function cannot accept a variable as a parameter, which is needed for your scenario because you want the client ID, not just the domain value. What I suggested will not help solve this. Sorry if this caused any detours for you to resolve this. Your next steps may be to…

Hi, Kriz. I'm sorry for the delay in responding; I was out-of-office for a while. I asked about Company-managed and Team-managed projects as they handle the connection between Epics and children differently...although that is changing and I believe the both can now check with {{issue.parent}} Let's assume you mean issues…

Hi @Jacey Harris I'm sorry for the delay in responding as I was out-of-office for a while. Thanks for the information about your rule's scope as global; that is likely the cause of this symptom... * Versions are created for each project, and are not shared between projects * Your rule can be triggered for any project…

I am using Cloud, and I do not have a Server/Data Center version to test this.

Hi @Yehoshua Silberstein Yes, and that was what was suggested by many of the posts here. Some were variations on that theme, based on either simpler workflow (i.e. one status per category) or no other changes close in time (e.g. checking updated) Kind regards, Bill

Hi @Joe Harrington There isn't anything built-in to do that. If you are always going back to the prior assignee, you could save the prior assignee whenever it changes, in a custom field and use that value later to revert. If your workflow allows multiple transitions, and you want to target one prior status (e.g. back to…

Hi @Jacey Harris Interesting...I retested and this worked for me in a free license, company-managed project. Please try to select the specific project in the Create Issue action to rule some things out. Also, some questions... * Is this in a team-managed or company-managed project? * What is the scope of this rule: global,…

Hi @[deleted] -- Welcome to the Atlassian Community! Are you using a company-managed or team-managed project? And...are you trying to do this for linked issues or parent/child relationships? If parent child, please try updating the lookup issues action's JQL to check for parent instead of linkedIssue. Kind regards, Bill

Hi, Vincent. Did you see this part of my response, describing how to use smart values for links? To use the Link Issues action to a smart value expression, type (or paste) the expression in the field and it will appear below the field. When finished typing/pasting, select the value below the field and it will be used.

Hi @Mateus Almeida -- Welcome to the Atlassian Community! Until such a feature is built into Jira Cloud, what you can try is creating an automation rule, triggered on Issue Commented, extract the mentioned users' accountId values, and then add them as watchers. To do this, you will need... * to use a regular expression to…

Hi @Gil Blau I am curious: what is your scenario leading to deleting the original issue? Specifically...if there is any work that happens on the issue in "project A" before the clone and subsequent deleting, won't you lose any Jira reporting on it? Thanks, and kind regards, Bill

Hi @Mateusz Czuchrak My understanding is: no, that is not possible to disable the update indication. When you link a Trello card to a Jira issue, it is creating a Remote Issue Link. All such actions are recorded in the history...because if they didn't, well...it wouldn't be an accurate history of what happened. Have you…

Hi @jherman Are you trying to set the resolution with automation for Jira Service Management? If so, I believe that is not currently possible, per this open suggestion: https://jira.atlassian.com/browse/JSDCLOUD-3701 Kind regards, Bill

Hi @Mathew Mullan -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? I ask, because... * This seems like "pushing" reminders, and may indicate there are other issues to consider if people are not aware/pulling on their own work. Perhaps this could cause unintended consequences. * To…

Hi @Olga Videc For your information, the link you provided is for the Server/Data Center of automation rules, and Matthew appears to be using Jira Cloud. Bulk processing in Jira Cloud is often done using the Lookup Issues action instead. Kind regards, Bill

Short version: this may not be possible with an automation rule due to the way the REST API captures changes to a list field. This seems to be the specifics of the defect @Jarosław Solecki [Deviniti] noted in this thread. Longer version: * I retested with Jira Cloud, using several scenarios of add/remove, and…

Sounds good! A lot about automation rules is experimentation and learning...especially as the documentation continues to improve :^)

Ah, I believe that is a known issue. The work-around/fix is: * clone your issue * branch to "most recently created issue"* add the watcher in that branch

Sorry if I was unclear: * that rule change will not help you get the value for the previous/from value of fixVersion. Here is why... When a field changes, an event is raised: "hey, this field changed!". That event can be used to trigger a rule because the rule is "watching" for that event. For example with an Issue field…

When your dashboard is in edit mode, add the wallboard spacer, and select the ... menu and Rename.

Hi @Rahul Jith Yes, and...to what @Jarosław Solecki [Deviniti] notes: {{fieldChange}} and {{changelog}} have values when there is an issue change, as captured by an automation rule trigger. With your scheduled trigger those smart values would always be empty as there was no issue change event: just a time-based one.…

Hi, Lukas. I cannot answer those questions. Your inspection of the different sites may provide the most information. For example, looking at the audit log and site log, what else is happening at the same time as the rule making updates, how many issues are in each instance, how often do issues change, etc.? In general, I…

Ha! If you found an old post indicating someone figured this out, I recommend replying to that post and ask for more info from the person. And as the vendor states it is possible/difficult, it seems reasonable you could ask them for an example by their support channel...if you are on the paid license.

Hi @Holly.McGovern -- Welcome to the Atlassian Community! There are two ways to resolve this, depending if you want to receive one email per issue, or one email containing all of the issues: * one email per issue:* As Nicolas suggested, add a JQL statement to your schedule * This JQL could also replace both of the…

Hi @Fred The {{^last}}something{{/}} structure allows you to conditionally do things inside of the list iterator. For example, {{#lookupIssues}}{{key}}{{^last}}, {{/}}{{/}} Will add a comma after each key value except for the last one; that is what the ^ last represents: not last. Please refer here for more information on…

Hi @Andrew K_ First thing, a disclaimer I am using Jira Cloud and am not using ProForma. With that out of the way... Looking at that documentation, there are a few warnings and disclaimers about what is not supported yet. As you are probably paying for this tool perhaps submit a support ticket to the vendor to see what…

Hi @Antoine Claudé-Pénégry -- Welcome to the Atlassian Community! If you want two rules to execute one after the other (i.e. you intend the first rule to complete before the second rule starts) try structuring the triggers to do that. Your second rule is triggered on change to the Epic's assignee, which could certainly…

Hi @Sambath SUN For a question like this, it may help to post images of your complete rule and the audit log details showing the execution. That will provide context for people trying to help. Thanks! Kind regards, Bill

Hi @Lukas This symptom seems like a coincidence/artifact of different instances. As others noted, automation rule triggering is event-driven, as is some automatic, issue view updates. I do not know of any SLAs about the rate of update...and... You note a free instance and a paid instance. Have you worked with your site…