Bill Sheboy Expert

Hi @Àlex Costa -- Welcome to the Atlassian Community! Have you tried using the if / else block with additional conditions: https://confluence.atlassian.com/automation/jira-automation-conditions-993924794.html#Jiraautomationconditions-ifelseblockIf/Elseblock And then use the Edit Issue action for each case to perform the…

Hi @Dimitrios Kouroumichakis For an automation question, it helps to post your rule in a single continuous image rather than in separate images. From what you show it is difficult to understand what is happening. Please try using a screen capture tool or a browser addon for scrolling page capture and re-post your rule…

Hi @Jimmy Seddon Thanks for the updates, and... As a small adjustment, Atlassian is renaming "Issue" as "Work" in some places and as "Work Item" in others. Please see the comments on the various threads for more information / concerns / etc. Thanks! Kind regards, Bill

Hi @Fiodar Krents -- Welcome to the Atlassian Community! I do not believe the built-in automation action to send a MS Teams Message captures the message ID to send back to the rule. Perhaps try calling the REST API endpoint directly to send the message using the Send Web Request action, and then check the response to find…

Hi @Abdelhafid CHRIFI -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single image for continuity * images of…

Hi @Garrison Thomson The audit log you show indicates the Summary field did not exactly match (i.e., equals) the text "New Hire Request" as it contains additional text for the person's name. Please try using the "contains" or "starts with" operator rather than "equals". Kind regards, Bill

Hi @Ni Zhang -- Welcome to the Atlassian Community! Your rule could use the field value changed trigger, watching for changes to the Parent field, and then use the changelog smart value to update the new and old parent Epics using branching and the Lookup Issues action. This is a very common community question, and if you…

Hi @Aleksandra Leesment As this is a very old thread, please create a new question using the "Ask a question" link at the top of the page. When you create your question, please note context is important for the community to help. Please post the following in your new question: * what version of Jira are you using: Cloud,…

Hi @Ben Culbert -- Welcome to the Atlassian Community! Usually, the Edit Work Item action can update a field in two ways: from the dropdown list or using "additional fields" with a JSON expression. But, it cannot to both for the same field in the same edit, as your rule shows. Please remove the JSON and only use the…

Hi @kalaimani What problem are you trying to solve by doing this? That is, "why do this?" Knowing that will help the community offer better suggestions. Until we know that... It appears you are trying to implement a measurement for time-in-status, including potentially pausing the measurement. Except for very simple…

Hi @James Dempsey -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.) * an image of your complete automation rule in a single image for continuity * images of…

Hi @Youngeun Kim -- Welcome to the Atlassian Community! The subtasks smart value is one where the data is looked up just-in-time when used, and it does not include all of the fields, such as time tracking ones. The same is true for the linkedIssues smart value. This is by-design and for performance reasons. If rules did…

Awesome; I am glad to learn it is working! If the suggestions helped, please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

One simple version would use basic HTML for a table, as you did in your original question. Adding that approach to the example I provider earlier, it could be this: <table border="2" style="border-collapse: collapse;" <tr> <th>Work Item</th> <th>Worklog Author</th> <th>Time Logged</th> </tr> {{#lookupIssues}}…

Once again: you are mixing incompatible smart value expressions / functions for logic and math. Please read the documentation links I provided. And...there is no {{else}} expression. The only format of the if() function which provides true and false values is this one below (the one without the pound sign #), and it is…

Hi @Jesper Skytte -- Welcome to the Atlassian Community! Short answer: When you want to provide the work items (previously called "issues") directly or send a key, then "yes": two rules would be needed. However...as "providing the work items" seems to send the keys as a list and then the trigger processing gets them to…

Hi @Altamash Heroli -- Welcome to the Atlassian Community! Adding to the suggestions from @Valerie Knapp there are no built-in sort or group-by list functions to help with what you asked. A marketplace app would be needed for advanced reporting like this. However... A workaround is possible if you know all possible work…

Thank you for the additional details as they help identify where the problems exist. Here are some suggestions: * The variable named latestVersionName should use this value for the first Fix Version in the first issue found from the lookup. Note this is a list-of-lists and so both first functions are needed.…

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

I recommend splitting this into four parts: * extract the year and counter from the version name in one of the issues * decide using conditional logic which year and number to use (as described earlier) * assemble the pieces together * create the version Based on the initial rule you showed, you should have all of the…

If you are adding the labels whenever the Description field changes, couldn't that cause prior values to remain in the Labels field? Back to what you describe: updating the labels this way with an advanced branch may cause problems from multiple work item edits in a short timeframe. It is better to perform a single edit /…

In that case, the found value must be split() on the commas to create a list for branching: {{issue.description.split("\n").match("\|ABC\|(.*)\|").split(",")}} Pausing a moment: what problem are you trying to solve? That is, why do this? The scenario you describe is sounding more and more like a contrived example, almost…

Oops...typo as the pound sign # is missing from my earlier post. Please use this: { "update": { "customfield_10003": [ {{#varSystemOwners.split(",")}} { "add": { "value": "{{.}}" } } {{^last}},{{/}} {{/}} ] } }

Thanks for that additional information. Please answer these questions: How is the Fix Version field changing for the work item in the Sprint when the rule runs? What should the rule do if there are multiple different versions assigned to the Sprint's work items, perhaps due to an entry error? With what you have described…

Hi @Chuck Kandzierski Just to confirm what changed for the sunset of the "Epic Link", "Epic Name" fields... * Epics are still called Epics * the "Epic Link" field was deprecated, and the "parent" field is now used for all parent / child relationships * in an import, use the "parent" field when mapping the import for the…

Please show what you are using in the Edit Issue action to add the labels. Are you trying to match multiple values with "ABC" or a single value? For a single value, the branch should not be needed: just use the ADDREMOVE labels option and enter the smart value expression.

Hi, @SilkeS Thanks for confirming about the account links. Last time I "switched" I lost some (not all) of my history, and can no longer access the old accounts to link them. Lesson learned! :^) For event registration, recently I tried to register for an Atlassian webinar in January / February; here is one of the community…

Hi @Gomez, Jorge (J.) -- Welcome to the Atlassian Community! When is the label being removed? What was the person doing just before that happened? From what you described, it seems likely that an automation rule or workflow action is doing this. And, if the rule's have been modified where the actor is set to "person who…

Hi @Bruce Fint My understanding is actions (called Tasks in Confluence) operate using mentions, and so if the user is watching Jira / Confluence, I believe they will be notified. If not, you could create an automation rule with the Task Created trigger, and notify the correct person using the Send Email action using the…

The list functions you show do not exist: sort and reverse. When one wants to order the results of the Lookup Issues action, an ORDER BY clause is added to the JQL. But that will not help for this scenario because it cannot sort a list-of-lists (i.e., Fix Versions is a list within the lookup issues result, which is also a…