Bill Sheboy Expert

Hi @Keith Thomas If you review the sources I provided and look at an example Jira Scrum Board, you will find the parent work item associated to items on the board can display in various ways (e.g., on each item, in swim lanes, etc.), although not in the way shown in your image from that site. Without getting into a…

Thank you for confirming the symptom, @Jader Peixoto Volkmer To add additional Request Participants, please only use a JSON expression and not selecting the field from the dropdown list in the edit work item action. How are you identifying the additional people to add to the Request Participants? That information will be…

That is curious...I just tested that in a rule with Jira Cloud and it worked as expected. This suggests that either there is something else wrong in the rule or the startDate smart value causes errors when used standalone. Again, without seeing the entire audit log from the rule execution, there is no way for me to confirm…

Please copy-and-paste the text from your audit log to provide more context. Thank you.

Hi @Keith Thomas Jira boards display work items based upon a filter. For Jira Scrum boards, they additionally filter to only display the items in the active sprint. For any Jira board, the columns represent the mapping of Status values to each column. There is no column on the left side for the parent Stories: that is a…

To which query are you referring that showed the error? The simple rule I suggested only used a query to access the single issue you showed in the log: key=TT-5

Hi @Marcus Toepper Without seeing your actual rules and the audit logs, diagnosing any looping is difficult. You may just be missing a conditional check after a rule triggers to prevent it from further processing. If you post your rules and logs, the community can offer better suggestions.

Hi @Cooper -- Welcome to the Atlassian Community! Short answer: If all of the subtasks have the same "duration" and you know the relative amount to shift the dates, that can be done with an automation rule branch. Otherwise, solving this is quite difficult, and perhaps impossible with built-in Jira features. When…

Hi @Sarah McDonald -- 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, JSM, etc. * an image of your complete automation rule in a single image for continuity * images…

Thanks for confirming you are using Jira Data Center! I checked the documentation, and the startDate appears to not be available to automation rules with the fixVersions smart value. issue.fixVersions Fix versions of an issue as a list. See accesing multi-value fields. Properties for versions include: name, description,…

Which version of Jira are you using: Cloud, Server, or Data Center? That impacts which fields are available. Next for the rule you describe, the Lookup Issues smart value would not apply as you are not using that. Instead, please try this to just get the earliest startDate from the Fix Versions in the trigger issue:…

I believe we are aligned on the scope, @Stephen_Lugton as three rules are needed for full coverage (and / or subject to automation engine problems and when Atlassian adds calculated fields): * triggered on work item created, set the initial value using the calculation * triggered on field value changed, for any input…

Hi @Scot McGavin I believe the automatic set of the Component feature works from the backlog when the filter is unambiguous and the field is on the work item create views. For other paths, a brute-force approach with an automation rule would be to add a check on the people compared to the {{initiator}} smart value, and use…

Thanks for that information, and...even though you cannot post images due to the air-gap environment, you could copy-and-paste the audit log details text showing the rule execution. That may provide more context. Until we see that... The correct smart value for the Fix Versions field is plural, and your value is not:…

Hi @Stephen_Lugton Please re-read my post as I describe two rules: Use two automation rules (one triggered on work item create and another on source field changes) to calculate the value Kind regards, Bill

Hi @Ryan Willms For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single…

Hi @黃惠婷 -- Welcome to the Atlassian Community! The most likely cause of that symptom is a known, racetrack timing problem with the Work Item Created trigger (and others). What happens is the rule starts before all of the data is available, leading to unexpected behavior, permission errors, and sometimes even a work item…

Hi @Luna Thanks for this information. The changes seem primarily to support inexperienced automation users, however, it it could still confuse them regarding missing context for smart values. What has the team considered for these ideas? * When a rule component is selected and using this feature, only show the possible…

Hi @Darryl Lee As you are aware from other community threads and open JAC suggestions to prevent "marketing" prompts, this is definitely an ongoing problem. A related problem is the confusion and extra work created by pushing UX experiments as the previous opt-out of "lab features" toggle no longer works predictably. These…

Hi @Marcus Toepper -- Welcome to the Atlassian Community! Without first seeing any of your rules and their audit log details and knowing your Jira version... Although it is possible to sequentially run a set of automation rules, that solution approach can be brittle for several reasons... First thing, when rule #1 performs…

Hi @Holly Rademacher Atlassian is currently building a feature for calculated, custom fields. You may watch / vote for that item to see progress here: https://jira.atlassian.com/browse/JRACLOUD-61966 Until that is available, you could... * Use two automation rules (one triggered on work item create and another on source…

Thanks for that information. I recommend starting with learning about rules and creating a simple test rule to confirm it works as you want. Then add additional cases and handling. As you have not written a rule yet, I recommend pausing to learn about automation by reviewing the documentation and any of the free training…

Hi @MARCO ANTONIO TOTH -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an…

Hi @Corey Hemingway Based upon the work item keys shown in the audit log, this seems to be a timing problem of some type: * story PD-22708 is created * and when it is branched to as the most-recently-created item, the next key used for the sub-task is PD-22710... * which means the story PD-22709 was created in the time…

Hi @mathew Pelchat -- Welcome to the Atlassian Community! Without seeing your entire rule, I hypothesize you are using the Lookup Work Items action to gather those linked features, and trying to find the date from there. Please note the lookup result is a list of work items, and the fixVersions smart value is also a list…

Hi @Sean Hearne -- Welcome to the Atlassian Community! That is possible with an automation rule, although it is not simple it is doable. First thing, when do you want to do this? That is, what is the triggering event to rank the work item to the top of the backlog? Next, there is a REST API endpoint to change the Rank…

Hi @julie_calboutin -- Welcome to the Atlassian Community! First thing, I recommend obscuring / removing your webhook URL in the images you posted. Next, for fields such as Summary and Description, remember to add the JSON encoding function when including them in the custom data:…

Hi @John Bradley That is not possible yet, and here is the suggestion to add the feature: https://jira.atlassian.com/browse/JRACLOUD-94173 Kind regards, Bill

Hi @Gabriel Carrillo -- Welcome to the Atlassian Community! Please carefully review the rule's audit log and note what @John Funk suggested: Your rule log shows creating the Task with no problem and then failing to add the checklist items to the Subtask. Please check the Subtask work item type configuration to confirm it…

Hi @Dominic Douglas -- Welcome to the Atlassian Community! Adding to the other suggestions provided, and assuming you are using a company-managed project... Since the Atlassian change to consistently use the parent field to link parent / child work items, only one rule is needed for this scenario. When a child is updated,…