Bill Sheboy Expert

Hi, community, and...thanks for filling to respond to Cyril's follow-up questions! (I was offline for a while due to power and interwebs outages in my area :^)

Hi @Jared Schmitt For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution Until we…

Hi @Mihai Vasile -- Welcome to the Atlassian Community! I agree with the suggestion that requiring the Due Date when the work item is created might be better than sending reminders later. When you still want to send reminder emails, please consider sending one email per reporter per day in case they submit multiple work…

Hi @Staffan Bergh -- Welcome to the Atlassian Community! When using the Field Value Changed trigger with multiple fields selected... * The rule will trigger when any of the fields changed (i.e., it is an OR check) * The rule will trigger for each field changed, and thus multiple rule executions when the fields are changed…

Hi @Sheri Seldes -- Welcome to the Atlassian Community! I recommend using a Lookup Table to map the field values to the Slack channel, and then use that in the rule action. This will make maintaining the rule easier. Please look here to learn more about lookup tables:…

Although you could add a custom field (or label value) to indicate "Sprint 1", etc. that may not be enough information. In Jira, a Sprint has a defined timeframe and scope, distinctive reporting, and each work item could carryover to multiple sprints. Those things are not easily possible with just a single custom field or…

Hi @Cyril James I recommend starting with a conversation with the entire team, including the people who "want to start timeboxing work and want to run Sprints": * What problem are they trying to solve? That is, why do that? * What do they believe would be different, and why do they believe that? * What ideas-to-try does…

Hi @Kristen Stephens -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log…

Thanks, @Erika Reategui In the Edit Work Item action, you would only need this to set the value: { "fields": { "customfield_11976": {{triggerIssue.customfield_11283}} } }

Perhaps I did not explain that well... When you have a list of historical assignees and a list of people on a team, you can use the "overlaps" technique to find the person to whom you want to assign. That would eliminate the looping and most of the conditional logic.

Hello, everyone! I just did a quick check in the JAC and Ecosystem backlog spaces and found no suggestions / defects to add the transition ID to the appropriate endpoints to support this capability.

@Ajay Dev -- Please post images of your updated complete rule, the Edit Work Item action, and the audit log details showing the rule execution. Also, is your field visible on the edit work item view?

Hi @Boyan Iliev Would you please show images of your entire rule (in one continuous image) and the audit log details for the entire rule's execution? Those may provide better context for this scenario. Until we see those... I recommend using the Assign User action with the accountId as a variable / smart value for this…

Hi @Thu Nguyen -- Welcome to the Atlassian Community! The community needs context for automation rule questions to provided better suggestions. Please post the following: * an image of your complete rule in one single image for continuity * an image of the complete Edit Work Item (or Create Work Item) action where you use…

Hi @Erika Reategui From what you show, there is definitely something incorrect in either the rule export or the JSON expression you used. Let's try this: * What are the types of these fields: text, number, select-option, etc.? * Please post the JSON expression you are using as plain text

Hi @Trudy P Claspill Until we see Marc's answer... I do not believe what you describe is possible for your scenario without a transition rule to set / update a field to note the specific transition. * The changelog entries do not contain the transition ID: they only have the from and to status names / IDs * And, the REST…

Hi @Fabio Racobaldo _Catworkx_ I have noticed several symptoms for a few weeks, independent of the recent AWS incident. These include: * overall slowness of page sections from the Forums home and question / article load * missing items from the selected groups / products in "Your Community Feed" * failure to load…

Hi @KC Wong Yes, and...to the suggestions from @Marc -Devoteam- I recommend adding a trim() function after the split(",") to handle any possible parsing variation of a comma versus a comma-space delimiter. Kind regards, Bill

Hi @Ajay Dev The rule you show is trying to set the field with the Edit Work Item action using both the dropdown field list and a JSON expression. Only one of those methods can be used at a time for a specific field within a single action. Try removing the JSON expression and just using the dropdown selection. If that does…

Hi @Samuel Gatica _ServiceRocket_ Where in Atlassian Automation were you able to use nesting of double-curly brackets? My understanding is that expression will always evaluate as invalid, with the error: Unable to render smart values when executing this rule... Kind regards, Bill

Awesome; I am glad to learn that helped! FYI for my earlier note about "lookup tables are normally plain text"...Unlike a created variable, lookup tables preserve the typing of the values. You probably typed in the text / values for the lookup, and so they were plain text strings. If instead the value came from a smart…

You are quite close to the answer! Your custom field is multiple-selection, and thus the values are iterated to add in the JSON: { "update": { "customfield_10032": [ {{#issue.customfield_11515}} { "add": { "id":"{{accountId}}" } } {{^last}}, {{/}} {{/}} ] } } Note the extra part to conditionally add a comma separator for…

Hi @michelle_brideau -- Welcome to the Atlassian Community! The values in created variables and lookup tables are normally plain text. To use them as a number they must be converted with the asNumber function. Please try adding that after the get() function call:…

Hi @Erika Reategui Are your work items in different projects: the JPD project and another one for the linked item? If so, please note even though the fields have the same name, they are different in the configurations for those projects. The rule will need to use a JSON expression to copy the value rather than use the…

Hi @Martin Cleaver One possible cause of this symptom is the known racetrack timing problem with the Work Item Created trigger (among others). That is, the rule can start running before the work item data is fully available / stable for the rule to use, leading to incorrect conditions, actions, and weird errors...such as…

Hi @Sebastian Krzewiński As a variation of the other suggestions offered... When you check for any existing matches to the ticketID value in the webhook data, what should happen when there are multiple matches found? * trigger: incoming webhook (with custom data) * action: lookup work items, with JQL to match to the field…

Hi @James Parkin Regardless of how you decide to update the existing work items, I recommend next doing a bit of root cause analysis (RCA) on why the creates and resolutions / closures are delayed. That may reveal opportunities for process improvements and / or automation to add the incident-work-item creation to your…

Hi @arielei Short answer: In my opinion, unless there exists a very sophisticated, marketplace app which has up-to-the-minute handling for Cloud automation changes to do this, an export-edit-import approach may work, although every rule may need to be checked for safety. If your license level is high enough, perhaps ask…

Hi @Camilo Gutierrez -- Welcome to the Atlassian Community! You cannot reorder them without changing the board filter. You can filter them, depending upon your project type... * For a team-managed project, you may...* On the backlog, select Filter, and then Parent to select an Epic, or * Select Status to filter on that *…

Hi @Katie Kusjanovic Short answer: as you appear to be on a Premium license level, I recommend working with your Jira Site / Product Admin to submit a ticket for Atlassian Support to take a look, using the main URL or through your customer rep: https://support.atlassian.com/contact/#/ With the extent of that AWS outage, I…