Bill Sheboy Expert

Hi @Andreas Deogarevic What have you done thus far to solve this need? If you started an automation rule, please post images of your rule, the audit log details, and explain what is not working as you expect. If you have not started a rule, you have essentially described the steps. Please look at this documentation and…

Hi @jonas.santana -- Welcome to the Atlassian Community! For a Jira Scrum board (and backlog) the status category is not relevant for those counts. Instead the mapping of the status values to the board columns is what matters: * left-most board column: those are counted as not started * right-most board column: those are…

Hi @Adam_Sterrie That depends upon how the permissions are configured. The default configuration is site admins count toward usage. Please read this article; it has a specific section to explain how to remove the site admins.…

Hi @Gema Ruiz In that case, 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 ideas. Thanks!

That error is describing the problem: the rule is trying to edit issues but none were provided. You would need to decide which issue you want to update, write a JQL statement to find them, and then use that JQL in the trigger.

@Benedikt Ostwald my ideas depend on if a team using Scrum or Kanban practices. If a team is using Kanban practices, one approach is to distinguish "working" and "waiting" columns on the board: the board matches how the team works. That could include columns named "X completed", where X refers to a prior process step. For…

In the message dialog for posts, you will see an image icon with "Insert Photos" to help. I am not using JSM currently and so cannot test this, but I wonder if you use the advanced edit with JSON to update the attribute name as there is no action to directly do that with a rule. Looking the template library I also see no…

I am glad to learn you have something that works. Another way to do that would be to use the match() function with a regular expression, as that will be easier to adjust in the future... As some Atlassian employee posts in the JPD community pages indicate automation work is in progress, I also wonder if that format of that…

Hi, Valeria. You noted, "...this kind of tickets come from an external tool." Would you please explain that further? Are these still all Jira issues? What is the format of your description field? Knowing that will help to suggest how to parse these keys / values out for use. Perhaps provide an example and explain what /…

Hi @michaelreiff What problem are you trying to solve by having the Sprint ID value? Knowing that may help the community to suggest alternatives. Thanks! Kind regards, Bill

Hi @Ajay Thakur -- Welcome to the Atlassian Community! Have you asked the people if they changed their notification settings to disable mention alerts? They may verify that by the following: * from their avatar image at the top-right of the page * select personal settings * in the notifications area, check if "Someone…

Hi @Daniel Lopez Would you please post an image of an issue with this symptom, showing the sprint field and complete issue history, in one image? That may provide some context. Thanks! Kind regards, Bill

Hi @Rajkumar Dalwai What type of project are you using: company-managed or team-managed? You may find that information at the bottom-left side of the page's expanding area. Company-managed projects use the "Story points" field and team-managed use the "Story point estimate" field. Kind regards, Bill

Hi @Coco S Chaussée Looking at your expression, there is a parenthesis in the wrong place. It appears my original post had an error, and I have corrected that. Tip: it helps to create expressions like this in a text editor which shows matched / mismatched parentheses and brackets. Here is the corrected one:…

Hi @Dennis Hansen Yup, that is the "date" format for Jira Product Discovery (JPD): it is a text string representing a range of dates...with no typing or attribute information (at least in automation rules). You can find other posts where customers used the text functions in automation rules to get at the values in the…

Hi @James -- Welcome to the Atlassian Community! If you mean in regards to automation rules, I would answer your questions with: No - there is no complete list No - there is no tool / list to show which operators can be used with each Smart values are context-specific, and so your installed Atlassian products, marketplace…

Hi @Brian Taylor There is a specific trigger to detect when an issue is assigned: https://support.atlassian.com/cloud-automation/docs/jira-automation-triggers/#Issue-assigned Please try using that one instead of Issue Updated. Kind regards, Bill

Hi @MURUGESH S Are you trying to create the tasks with an automation rule, setting their due dates based on the epic's due date (or "now") plus / minus the estimated effort duration? If so, you can do that with a rule, using the date / time…

Hi @Nici Phillips -- Welcome to the Atlassian Community! You may do that with an automation rule, triggered on issue commented, followed by the send email action. To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @Natalia Melnichanskaya -- Welcome to the Atlassian Community! It may help if you post an image of the dashboard showing the error. That may provide some context for the community to offer suggestions. Which gadget on your dashboard is showing this error message? And is it one of the built-in gadgets or one added by a…

For the audit log, when you are viewing the rule, the audit log will be shown at the top-left. Find the one for the rule execution, and select "Show more" to see the details of the steps run and what happened. Regarding rule scope, if you can identify the projects impacted by the rule, you can then work with your Jira site…

Hi @Rudy Holtkamp That would work outside of the branch shown, and after it issue created in step 2. But once inside the branch on "most recently created issue" the smart value {{issue.some field}} will work as expected. Kind regards, Bill

That would update the current Epic, as with your earlier rule. Another section would be needed to update the previous epic, where the key is probably {{#changelog.parent}}{{fromString}}{{/}} And so another rule section would be needed after what you show * branch: on JQL of* key = "{{#changelog.parent}}{{fromString}}{{/}}"…

Hi @Gary Fan What is your relationship to the vendor of the product you are suggesting? If you are employed by them, in accordance with the community guidelines for marketplace and solution providers, please ensure you disclose in the text of your post your relationship to a vendor when recommending their products. Please…

First, several questions about what you are showing. Is the "Remaining Time" field intended to be a percentage value? For example, a number such as 50.0 Is the "issueDueDateandtime" a custom field in the issue? The built-in "Due Date" field is a date field only. Is "issueStartDate" a custom field in the issue? The built-in…

Hi @Ron Aisen Context is important for automation rule questions. 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…

Hi @valeria marcon That might be possible. Such a rule would use a regular expression and the match() function to extract the issue keys from the description field, and then use an advanced branch to iterate over them to perform the edits. Would you please explain the problem you are trying to solve? That is, "why do…

Hi @Бабій Олександр Context is important for automation rules. 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…

Hi @Heather Millar Would you please post an image of the audit log showing two cases when the rule works as expected and when it does not? That may provide some context to help. Until we see that... You note the issues (epic and stories) are in different projects. In that case, this rule must be either global or…

Hi @Heather Ronnebeck Without seeing your rule specifics, I believe you do not need any Re-fetch Issue actions in the rule. That action is used for a couple of reasons: * When a rule edits the current issue, and wants to use the updated fields later in the same rule, the re-fetch will reload the data before proceeding *…