Bill Sheboy Expert

Hi @Coady Krzysztof -- Welcome to the Atlassian Community! The built-in features of JQL do not support comparing fields. It is an issue search language and not an actual SQL. The possible workarounds for this depend upon how often you need this capability and willingness to spend money / time: * need it one time* Export…

Hi @Omri Zeman What you describe may happen when there are newlines in the comment as the automation rule match() function does not consistently handle those well. The solution is to replace the newlines with spaces before the split(): {{issue.comments.last.body.replace("\n", " ").split("…

Thanks for that information, and... Based on the rule image you show, the Edit Issue action is trying to modify the Original Estimate field twice: once from the field dropdown list and once with JSON. Only one method may be used at a time for a specific field. I recommend removing the JSON and using just the sum from the…

No, as the plural {{issues}} smart value is used with Jira Server / Data Center automation. For Jira Cloud, the Lookup Issues action or Send Web Request is how issues are handled in batches. FYI...when asking questions it helps to include information about your Jira version and project type. That will help the community…

Hi, Emily! Please see my earlier post with the step after the condition to perform the edit.

In your question, you asked about using the milliseconds format, which is an integer number since the start of Epoch time (i.e., a UNIX timestamp). Returning to Trudy's question: what problem are you trying to solve? And what would be an example date / time format that would help you solve that? Knowing those will help the…

As that field is an integer, the asNumber function should not be needed for this to work. Let's confirm that attribute is correctly interpreted as an integer (number) by the rule... Please add a write to the audit log with this and then retest: is Review Frequency a number: {{object.Review Frequency.isNumeric()}} That…

Hi @John O’Brien For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image, * images of any relevant actions / conditions / branches, * an…

Hi @taslima.uddin Your question seems to be about using the views in Jira Product Discovery (JPD). The views display the Ideas based on the filter options selected. And so Ideas do not "move" between views; they display when their fields match the filter. Please change the fields of the Idea to make it display in the…

Hi @mohit.gambhir -- Welcome to the Atlassian Community! Do you want to see the counts by month or the issues for the month? You could try the "Created vs. Resolved Chart" dashboard gadget, setting the reporting period to be Monthly. This will show the counts, month-by-month. To see the specific issues, select a month on…

Hi @Edwin Andrew -- Welcome to the Atlassian Community! What version are you using: Jira Cloud or Server / Data Center? Based on what you describe, I hypothesize you are using the Server / Data Center version. Automation for that version does not yet support custom fields with the Lookup Issues action, and here is the…

Hi @Mareli Please try this one: {{#now}}format="toMillis"{{/}} That may be chained with other function usage, such as this: {{#issue.customfield_12345}}func=plusDays(2), format="toMillis"{{/}} Kind regards, Bill

Please use the Log action to write test expressions to the Audit Log, rather than adding comments. When comments are added, formatting is modified / interpreted, and makes diagnosing rule problems more difficult. https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action This is one reason I…

If you do not have JSM, the rules would need to implement any SLA logic "manually", using custom fields, scheduled rule triggers, etc. That is likely to be a brittle solution as a manual field change by a person, a simple rule error, or an Atlassian outage will halt rules and invalidate your SLA handling. I recommend…

Hi @Corey Hampton In your automation rule, please try using a Lookup Table for that type of field-to-field mapping: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798 Kind regards, Bill

Please post images of your complete, updated rule and of the Edit Object action. Those may help to see the current context. Thanks! And as a tip: when writing diagnostic values to the audit log, add clarifying text to make it easier to compare to the rule later. For example: here is my field: {{issue.myField}}

Hi @Philip Abdalla -- Welcome to the Atlassian Community! That information is stored in the changelog for issues, and it is difficult to access for reporting use in Jira. How you solve this need depends upon ability to spend time / money: * You note using a Python script. And so you could try calling the REST API endpoint…

Hi @Daniel Newman Smart values like that are listed under the "development" section in the documentation: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--version-- Kind regards, Bill

Hi @Renata_Getint Your post appears to be from an automated / chat-bot source. Please see the community guidelines regarding disclosure of the source for such content in the text of your post: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Kind regards, Bill

Hi @Omri Zeman What is not working as you expected for the rule shown? Perhaps also post an image of the audit log details for the rule execution and the rule details at the top to provide context. Rules like this trying to update multiple levels are typically recursive, for example allowing an update to a Subtask to…

Hi @peter dassenko -- Welcome to the Atlassian Community! There is no built-in feature to sum the fields for an Idea merge. One possible workaround is to use an automation rule, triggered on Issue Linked: * Merged ideas are moved to the JPD Archive, and not deleted from Jira * After a quick experiment, I observe each…

Hi @Francesco Arieta Team-managed projects do not have the Card Layout, or most of the other board configuration features. That is a feature of Company-managed projects. Please read this documentation to learn more: https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/ Kind…

Hi @Selena Farris That is not possible for a team-managed project, Kanban board. Here is a suggestion to add the feature: https://jira.atlassian.com/browse/JRACLOUD-85694 There are pre-sets to allow show / hide specific fields for team-managed projects under the View Settings, but not for the Story Point Estimate field.…

Thanks for that rule image, and it shows you can use the bulk-handling feature: * Move the JQL from Lookup Issues action to the Scheduled Trigger, ensuring you enable the bulk-handling option and clear the one for "only include issues that have changed..." * Remove the Lookup Issues action * In your email action, change…

Hi @Steve Holland There is a state attribute for that trigger, {{pullRequest.state}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/#--Pull-request-- However, I recall from some other posts and suggestions it does not capture "draft". I recommend first experimenting by writing that smart…

Hi @Rebecca Lewis I hypothesize that change is related to the recent addition of the Due Date to company-managed project (CMP) boards, even though changes to "work health" and "sprint health" is not specifically described in the weekly release blog:…

Hi @Johanna South -- Welcome to the Atlassian Community! When I did a quick check, the one you tried returned an empty components list for me also...but the other ones seemed to work, such as for scheduled maintenance, incidents, etc. Have you used the components one successfully in the past? Here is the full list for…

Hi @Nava Bar-Sagi Adding to Trudy's suggestions... Those fields are not available with the Lookup Issues action for Jira Data Center. However, if you only want to send an email with the issues, the bulk-handling feature with the plural {{issues}} smart value might…

For Rich Text...under the "Formats" dropdown there is a "Code block" option for fixed-font. Yet that "zaps" spacing when pasted in as text...requiring aligning text. You could also try the HTML format to see if that helps preserve it better.

Short answer: maybe. Which is why I suggested reading Trudy's article and comments to it. If you have 3 issue type levels, 3 rules might be better for this scenario. Beware: longer explanation ahead :^) Scenarios like this are essentially trying to re-implement features of purpose-built, project management tools using…