Bill Sheboy Expert

Hi @Fuji Ignoring for the moment the problems of using story points on subtasks, rather than with stories... Your JSON and the smart values in the rule are invalid, as the error message indicates. Please look here to learn the correct syntax for updating a number…

Hi @Shannon Bradley That error is telling you the math expression's inputs collapsed to null, leaving only the * remaining. What are the types of your fields? If they are numeric, please remove the .value from each of those fields in the math expression, as that is used for selection fields (i.e., drop-down lists).…

When an issue is removed as a child from an Epic, the trigger is different...and so this rule would not trigger. To handle the case of adding (or removing) child issues from an Epic a new rule is needed. For example, trigger on a change to the epic link (or parent) field, check if the issue is not an epic, and then use the…

Please move the Re-fetch up to immediately after the trigger, and then re-test: * trigger: issue created * action: re-fetch issue * condition: issue type equals Sub-task * action: edit issue fields for Components

In that documentation article for advanced edit with JSON, it describes how to check the edit metadata. That will show which operations (add, remove, set) are supported for a field. Please check that to confirm what is possible. If that does not help, you may need to work with your site admin to contact Atlassian Support…

Would you please show the entire body of your request? I see no spaces or closing quotation mark in what you have posted.

Hi @Rafael de Aquino Cunha -- Welcome to the Atlassian Community! If you are in fact creating a board for only your use... A board is a view of issues, based on a saved filter. If you want the issues displayed in a particular order, you may add an ORDER BY expression to the saved JQL filter. This would match what you…

The syntax for your JSON is not quite correct. (Please note the documentation only shows the details for each field type, and does not repeat the "wrapper" code for each example.) A full example would be this. Please add your account id value. { "fields" : { "customfield_10702" : { "id" : "yourAccountId" } } }

Hi @Mariam Matiashvili -- Welcome to the Atlassian Community! IMHO, this depends on the team and product owner's (PO) working methods...and the different scales at which you are looking for information. As a PO, please consider what do you want to know, why that information, how would you want to see it / use it, and when…

Well done; you almost have the whole rule completed. Please try adding a Related Issues condition for that test, inside the branch and before the action to create the sub-task. The idea is to check if there are no assigned sub-tasks for your {{Reviewer}} before proceeding. The specifics to try are: * Related issues: JQL…

You could also consider limiting the scope, such as only use the Due Date at some levels. That would reduce the complexity and may still provide you the benefits you want.

Hi @Petar Cvetanovic For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer…

Hi @sadhana.chittibabu This appears to be a duplicate of your other question: https://community.atlassian.com/t5/Jira-Core-Server-questions/add-text-indent-when-updating-comments-using-rest-api/qaq-p/2533988 Please consider closing out this one to help focus the suggestions. Thanks! Kind regards, Bill

Hi @sadhana.chittibabu I do not believe tab is supported in the markdown for the Jira text fields. You could try entering spaces for your indents, or investigating marketplace addons which can parse that markdown. Kind regards, Bill

Please post the following: * an image of your complete rule (ideally in one image), * an image of the edit issues action, and * an image showing the audit log details for the rule execution. Those will provide context to help explain the symptom. Thanks!

Hi @BenWade Adding on to Dave's suggestions... This is a lot of issue type levels to roll-up, and so I recommend defining your assumptions before writing any automation rules for this. That will help to identify test cases and limitations to the solution. For example: * Have you discussed this need / scenario with your…

Hi @C S Seshagiri Please post an image of the audit log details, showing the rule execution. That may help explain what you are observing. And as your explanation of the rule includes more details, I suggest posting an image of the entire rule, in one image. That can be done with a screen capture or browser addon capable…

Would you please post images of your complete rule, the actions with the edits, and of the audit log details. Those may provide context to help explain what you are observing. Thanks!

Hi @Marc Isikoff I recommend creating a new question, showing your complete rule and audit log details, and perhaps link back to this thread. That will get the most visibility for the community to offer suggestions. Thanks! Kind regards, Bill

Hi @Oussema Marai -- Welcome to the Atlassian Community! Slack has its own user accounts, independent of Jira users. And so this is not a simple problem to solve with automation rules. Please see this how-to article from an Atlassian team member on accessing the Slack information to do…

Hi @Inetinfo Inetinfo You might be able to do this with an automation rule. The rule could be triggered on changes to the priority field, and use the changelog entries to populate your custom field. This would only have the values for changes after the rule is implemented. Please look here if you want to try that…

Hi @Jenni Chen It is possible this is a timing issue. The Issue Created trigger can fire so quickly the issue data is not available at the time the rule runs. This can cause later rule steps to not work as expected; for example, perhaps the parent is not visible / set yet for the copy of Components. The work-around for…

Hi @Brad Dobyns -- Welcome to the Atlassian Community! I recall the Atlassian team is "in progress" of making changes to how those fields are summed on the backlog view (to include child issues)...perhaps something is bent / broken. I recommend submitting a ticket to Atlassian Support. You appear to be on a paid license…

At this point, I recommend working with your Jira site admin to submit a ticket to Atlassian Support, including a link to this thread. If you are on a paid Jira license, your admin can do that here: https://support.atlassian.com/contact/#/ They may see something we are missing in the field or rule configuration. When you…

Hi @Manikandan -- Welcome to the Atlassian Community! One way to do this is with an automation rule, incrementing the created date by a number of business days: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ To get you started on creating your rule, please refer to these documentation…

Hi @Ariel 韦曼曼 (PMO) What problem are you trying to solve by doing this? Knowing that may help the community to offer suggestions. Until we know that information... That is not possible using rule actions directly. There is no "delay rule execution" action. There are a few possible work-arounds: #1) A possible work-around…

Hi @Hall_ Courtney A_ -- Welcome to the Atlassian Community! I recall the Atlassian team is in-progress of making changes to include child issues in the totaling of story points in the backlog view, and so that may be breaking other things. I recommend immediately submitting a defect for their support team to take a look.…

Let's checks some things first, as if they do not check out then the field cannot be edited with a Send Web Request to the REST API functions either. First, have you confirmed that your field is on the views for the issue type in the target project, CORD? Who is the actor for your rule? The default is Automation for Jira,…

Yup...that y-axis is a problem for this interpretation of a CFD, and it is the reason many customers either use a marketplace addon to draw these or build them using exports and history log pulls. The documentation indicates it is the x-range only which impacts the y-axis scale...but that is not always true. For some data…

Thanks for that information. For a multiple-select custom field, there are two syntaxes, depending on whether you want to replace all values or add additional ones. FYI there are typos in the documentation, so I amended the "add" version to make it more clear. To replace all please try this one: { "fields" : {…