Bill Sheboy Expert

Based on above, the calling rule is not sending the issue keys in the correct format for the trigger to use with the option "Gather issues from request". Please see this documentation for the correct format:…

Just to align on terminology... * Jira Query Language (JQL) is what you are using in the Scheduled trigger, and * JavaScript Object Notation (JSON) is what you are using in the advanced edit for the Edit Work Item action. Back to your question, let's confirm you are changing the correct field with that ID, using this…

Just to confirm, what are the types of your fields? A "People" type field in a team-managed project do not provide the email address for users in automation rules. Here is the defect / suggestion to fix that: https://jira.atlassian.com/browse/AUTO-519 And thus one workaround is to add a global / company-managed user field…

That feature does not exist yet. The suggestion is to add it to Jira.

Hi @Abhinav Mishra -- Welcome to the Atlassian Community! You have posted your question in the community forums and not with Atlassian Support directly. I recommend working with your Site Admin to contact the Atlassian Support team here: https://support.atlassian.com/contact/#/ In the interim, there is very limited…

Hi @Randy Michel There is an active incident impacting automation rules. You may want to wait for that to clear and then try your rule again. Please watch the incident here to see progress / updates: https://jira-software.status.atlassian.com/ Kind regards, Bill

Hi @paul -- Welcome to the Atlassian Community! Please try using the built-in Time Tracking Report; that can sum the original estimate values. If you need something different, please investigate: * a marketplace addon, such as a dashboard gadget to sum fields * writing a simple automation rule to sum the fields, and…

Hi @Robert Condon This is a long-standing defect for Scrum boards and the feature "Days in Column". The defects / suggestions to address this often close as "timed out", such as this one: https://jira.atlassian.com/browse/JRACLOUD-86901 The only workaround I can think of to improve the accuracy for a Scrum board is to use…

Hi @Svetlin As you are using a marketplace vendor's addon for the default values, I recommend contacting that vendor's support team to ask how to do what you asked. Kind regards, Bill

Hi @suneel babu First things first: pause to understand why the rule needs 65+ components / steps. Perhaps if you explain what problem your rule is trying to solve, that will help the community to offer better suggestions. Until we know that (or see your specific rule implementation)... Longer rules typically fit into…

How I changed the naming convention of my documents... Long ago in software engineering, we would review another engineer's code by printing out reams of paper to pore over, annotating it manually with highlighters and red pens, and finally type up our action items in a document. The documents typically had a standard…

Hi @Qin Han The emailAddress attribute for a "People" type field in team-managed projects is not available to automation rules. Here is the suggestion / defect to fix that: https://jira.atlassian.com/browse/AUTO-519 The workarounds depend upon the specific scenario: * when only one value is needed, call the REST API with…

Hi @Edivaldo Giacon -- Welcome to the Atlassian Community! It is not possible to remove the weekend days from basic timeline view. Here is a suggestion to add that feature: https://jira.atlassian.com/browse/JRACLOUD-91655 Kind regards, Bill

Hi @Imran Abedrabbo -- Welcome to the Atlassian Community! You are correct: the first one is easier than the other... There is a Task Created trigger for Confluence pages that may be used to create the work item (formerly called "issue") in a Jira project using the task's smart values. When that happens, the Jira work item…

Thanks for that information, and... Where is your rule located and what is its scope (in the details at the top)? That is, can the rule access the "IT" project's issues? If not, that would explain this behavior, and the rule must be moved or the scope changed to include that project.

v3 for a paginated list has them too. (It is just above the one you linked to ;^) https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-project-versions/#api-rest-api-3-project-projectidorkey-version-get

This is curious...and the trim() should remove the obvious whitespace characters. I tested this repeatedly (with different formatting) with Jira Cloud and it worked as expected. What version of Jira are you using: Cloud, Server, or Data Center? Let's find out exactly what is left in there that is causing the extra spacing.…

Hi @Darryl Lee Both the name filtering (by query) and the status filtering may be sent in the original endpoint call using parameters. Further list filtering may only be needed for more advanced name (or other data attribute) filters. Thanks, and kind regards, Bill

Please show an image of the audit log details, with all of the areas expanded, to show which rule steps happened. As written, your rule will stop when any condition is not met. Have you confirmed the Status values you are using in the JQL conditions for each subtask type are correct?

Hi @John Voita Short answer: no, that is not possible. As with any work item, a JPD Idea is likely constrained to a specific scope / goal, and so would map (through delivery work items) to one-to-many other work items. Linking to an entire project would effectively mean the Idea is unlimited scope (as work items could be…

Hi @Juan Falguera -- Welcome to the Atlassian Community! This is likely a timing problem, where the URL is evaluated / processed before the match() function completes. I have seen the same symptom in the request body and with the Edit Work Item, advanced edit with JSON. The mitigation for this is to first perform that…

Hi @Josh Drake Adding to Trudy's suggestions... You cannot add a second branch after the first one to solve this need because branches of this type run in parallel and asynchronously, with no guarantee of when they finish until the last step in the rule. And so the second branch will start before the first one completes!…

Hi @Jon Owens -- Welcome to the Atlassian Community! This could be a timing / racetrack error problem... The Work Item Created trigger can start a rule before all of the data is available for the rule's use. This can lead to rule errors or conditions not matching as expected. The fix is to always add the Re-fetch Work Item…

Hi @Isaac Ruffner -- Welcome to the Atlassian Community! If you use your request URL with an example query in a browser tab (or standalone tool), do you get the expected 3 results? If you write the webhook response to the audit log, do you observe the same results as the standalone call? Finally, that result of that…

Hi @Abimbola Oye -- Welcome to the Atlassian Community! There are two versions of the ceiling function: one inline (which may not help for your case) and the longer form one, ceiling(). You are trying to mix the syntaxes, which will not work. *…

Hi @Dave Tabron Yes, that is possible using an automation rule. Here are some tips to get you started: First, I recommend writing a JQL expression to find the Epics linked to an example Idea, excluding the Done status ones, and using ORDER BY to sort by that custom date field. Next, decide when you want this information…

Hi @Carla Gonzalez It is likely there is a newline, or a carriage return and a newline, at the front of the text. After you have removed it, add a trim() function at the end of the expression to remove them. The reason the characters cannot be added within the remove() function is because there are multiple ways that blank…

Hi @Dominik I just tried to archive an Idea with a rule and it worked for me, as you tried with JSON. When using a JSON expression to update a field, please note: Ensure the field is not selected from the dropdown list AND in the JSON expression, as only one may be used at a time for a single Edit Work Item action. Kind…

Hi @Alfredo -- Welcome to the Atlassian Community! In your second rule, please try using the function jsonStringToObject() to parse / convert the input: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#jsonStringToObject-- If that does not work, you may need to use other text functions,…

Hi @Hariharan Y 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…