Bill Sheboy Expert

Hi @Benoit Guyot -- Welcome to the Atlassian Community! Have you checked the settings for the report to confirm they include the status values which the issues where in on June 17th? For example, it does not appear your chart contains the Backlog status, and so those would not display. Kind regards, Bill

Hi @Derek Fields _RightStar_ The scheduled trigger does have a "Run rule" under the ... menu at the top-right, after the rule is published in the editor. There isn't a "run now" option in the rule list. Is that what you meant? Manually triggered rules are always from the context of an issue, even if they do not use it. And…

Hi @Roumena Polianova -- Welcome to the Atlassian Community! 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…

Hi @Surya Narayanan -- Welcome to the Atlassian Community! You may try using the {{changelog}} or {{fieldChange}} smart values with the syntaxes noted in the documentation, however that may not be accurate. There is a known defect that list fields like Fix Version do not accurately track the changelog when there are…

Hi @Aline Veyradier There is an open defect for this symptom which is being worked on now. Please watch / vote for this item to see progress: https://jira.atlassian.com/browse/JRACLOUD-84014 Kind regards, Bill

Hi @Yash Sheetal Bhandarkar First thing, what problem are you trying to solve by running this rule every 5 minutes? That seems like it would be overwhelming to the recipients. Next, as your rule is written it will send the email multiple times. This is because the trigger has JQL without the option selected to "simply run…

Thanks for that information to confirm the rule structure. The Issue Created trigger can fire so quickly that some information may not be available to the rule yet. I recommend adding the Re-fetch Issue immediately after the trigger to prevent any timing problems with it. Next, do each of your Send Web Request actions have…

Would you please post an image of the audit log details showing the rule execution? That may provide some context for what is happening. What type of project is this: company-managed or team-managed? What type of field is Assignee QA: user selection, People, something else?

Hi @Vitalina Ostapchuk -- Welcome to the Atlassian Community! Adding to the suggestion from @Ezgi Bayındır ... This is a common / straightforward scenario, and so I recommend you learn more about automation rules to help you create such rules for future needs. Here are some references to help you get started: *…

Please stop posting answers generated by bots, particularly for rules which are misunderstood. For example, the condition is incorrect and there is no reason to have the Re-fetch Issue action in the rule shown as apparently the bot's parser did not detect that.

Hi @Talha Eryasar -- Welcome to the Atlassian Community! Do you mean the status element, from the dropdown as "Add a custom status label"? If so, that is possible, and seems to be just the color-formatting markdown: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=texteffects For an example with the…

Hi @JD -- Welcome to the Atlassian Community! There are several ways to solve this: * using a saved filter which compares the PM field to currentUser() and ask each PM and PMM to subscribe to the filter on their desired cadence: https://support.atlassian.com/jira-software-cloud/docs/manage-filters/#Subscribe-to-a-filter *…

Hi @hdenenberg -- Welcome to the Atlassian Community! 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…

Hi @christine_meimari -- Welcome to the Atlassian Community! You may use the {{createdIssue.key}} smart value for that information: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--createdIssue-- Kind regards, Bill

Hi @Oliver Stutz Unfortunately, there are two story point fields in Jira after team-managed projects were implemented: * company-managed projects use the "Story points" field * team-managed projects use the "Story point estimate" field In the UI for team-managed projects, they inconsistently display as both names, causing…

Hi @admin-nwalter As you are showing a manually typed in version of your rule, versus images of the rule and audit log, the community will need to guess a bit in order to help... In the rule you describe, you write this value to the audit log in the second-to-last step: AND: Add value to the audit log. - Log message:…

Hi @Radu Ichim -- Welcome to the Atlassian Community! Before you invest time in creating an automation rule, I recommend pausing to learn why an import would clear the parent field. Otherwise using the rule is, at best, mitigating the problem and not solving it. Kind regards, Bill

Hi @Simone K. -- Welcome to the Atlassian Community! Will the subtasks all be assigned to the same person originally assigned to their parent Task? If so, could the subtasks all be assigned when they are created? If not, how do you know which subtask is next? That is, which one is "Subtask B"? If it is always the same…

Hi @Vysakh Balachandran -- Welcome to the Atlassian Community! I recall there is unsupported REST API to add a webhook for Confluence, but I do not know if that includes an event for adding a calendar event. You may want to check the developer community to learn if that is possible:…

Hi @Rui Passos -- Welcome to the Atlassian Community! That is possible for a company-managed project's board, where the project admin / filter owner can change the ORDER BY for the board's filter to what is needed: https://support.atlassian.com/jira-software-cloud/docs/jql-keywords/#ORDER-BY However if that is done, you…

Hi @YARON LEVY -- Welcome to the Atlassian Community! That error is telling you the rule(s) exceeded the service limit of 10 loop executions: https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ This limit helps prevent rule errors / runaway conditions leading to self-triggering rules or chains of…

Hi @Anthony Nguyen 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 ideas.…

Thanks for your extra analysis, Christian! Answering your last question, first...no, there is no way to read all possible responses as JSON. I recall there is an open suggestion to add a text function for rules to correctly interpret as JSON, allowing dereferencing by attributes at all levels / structures. Next regarding…

Yes, that is possible. You may test the issueLinkType with your JQL used to gather the issues, and then count them: https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Issue-link-type Please note well: many link types have direction, such as "blocks" versus "is blocked by". So check your specific link for…

Earlier you noted using the parent field to connect Epics to child issues. This is the default, built-in behavior. But your rule does not show that. If you are using the built-in parent field, please update your rule as follows: * trigger: issue transitioned to Closed * condition: issue type is one of Story, Task, or Bug…

Please see the information I provided earlier about configuring board columns with multiple statuses. If that does not help, you may want to meet with your Jira Site Admin to explain what you are seeking to learn if that is possible with Jira Cloud.

Here is a follow-up example with that workaround...assuming the answer is in the current response for the Send Web Request action. * create variable:* name: varHistory * smart value: {{#webhookResponse.body.changelog.histories}}field:{{items.field}}@@@{{items.from}}~~{{/}} That would produce a delimited, text string like…

Hi @Chris Short answer: in my opinion, there is no simple / elegant way to do this using the REST API functions in a rule, and saving the prior status in a custom field may be easier to implement and maintain. More information... The changelog for an issue could be quite long, and so you may not find your status field in…

Hi @Jill Vieregge When in the backlog view, there should be a dropdown list of Epics to the right of the Versions one. At the bottom of the Epic list, there is a slider to enable / disable the Epic panel. The faster way to do this is with the shortcut key "E" or "e", as that will toggle the Epic panel display. And, the…

Hi @Erica Robinson -- Welcome to the Atlassian Community! Please continue to use the format() function for that, incrementing the date, as needed. For example: Q{{now.plusMonths(1).startOfMonth.format("Q")}} or this one, to automatically add the Q: {{now.plusMonths(1).startOfMonth.format("qqq")}} Please look here to learn…