Bill Sheboy Expert

On the right side, first switch from Detail to List view by selecting the icon with the down arrow next to it. Then the Columns option is available.

On the right side of the page, there is a Columns dropdown list to add / remove fields. As you are a system admin, it will initially show "My Defaults" and "System". (Be careful not to change the System ones unless you mean to do so :^) Use "My Defaults" to initially select the fields. After you save your filter with a…

Hi @Avrohom Yisroel Silver If you save your filter with a name, that allows also saving the selected fields, field order, and sort order results. When you export, you may then choose to only export the filter fields. https://support.atlassian.com/jira-software-cloud/docs/save-your-search-as-a-filter/ Kind regards, Bill

I am unclear what to suggest due to what is not shown. How about this: what text are you searching for in issues? That may help indicate why this code started failing. The CONTAINS operator only works with some fields and has some limitations on what can be searched…

Hi @Oscar Sanchez To increment a custom, number field you may enter this as the smart value when you select the field from the dropdown list: {{issue.your field smart value.plus(1)}} The key is ensuring you use the correct smart value for your field. Smart values are name, spacing, and case-sensitive. And often the smart…

Hi @Iain Davidson Your work-around may be the only approach now...although there may be marketplace addons to do this also. I found several suggestions in the public backlog, including this 14 year old one to show a diff like source code (or at least like Confluence does): https://jira.atlassian.com/browse/JRACLOUD-20112…

Hi @michael seward That error seems to indicate whatever text you are trying to match with the CONTAINS ~ operator ends the expression (possibly due to an unescaped quotation mark) and so the JQL parser is expecting either AND or OR to continue. I recommend looking at your specific search text to determine if that is the…

Hi @Nathaniel Elliott 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 @Lean Li 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!…

Hi @Amed Moreno 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.…

Hi @malika.raupova Please look here for the current Jira REST API functions for users: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-users/#api-group-users Please note well: some of these are listed as experimental functions and so may be subject to changes. Kind regards, Bill

Hi @011_avinash Please ask the project admin to remove the fields from the view configuration if the team does not want to see them. They can be dragged off of the view, over to the right-side of the configuration view.…

Hi @Suzanne Cranfield 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 @Garn -- Welcome to the Atlassian Community! For Jira Server / Data Center, the lookup issues action only supports some fields at this time. Here is the suggestion to add more, which you may vote for / watch to see progress: https://jira.atlassian.com/browse/JIRAAUTOSERVER-877 When the lookup issues action was added for…

Hi @Norberto Lopes Cabaço -- Welcome to the Atlassian Community! For your question 1: no, they will not be notified, by default. If they are watching the issue they will see the change. As an alternative, an automation rule could be created which watches for that specific type of change and notifies the assignees (e.g., by…

Hi @Dietrich 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.…

Hi @Matti Desmet It appears you are using the status based on count, and so: * when there are multiple issues linked with on the Delivery tab, the numbers show * when there is only one issue linked, the status value names show, including Done. Kind regards, Bill

Hi @BHarak -- Welcome to the Atlassian Community! What does "low performer" or "high performer" mean to your team, org, and stakeholders? * Is someone who cuts a bunch of lines-of-code that provide no customer value a high performer? * How is someone doing who delivered features that saved only time for the team, yet the…

Hi @Lusine -- Welcome to the Atlassian Community! I am using Jira Cloud, not Server version, so please verify the following suggestions will work for your instance. Your Jira Admin can help. * CSV Import* Have you considered importing the issues, using a CSV file? The file would need to be updated so the subtasks are added…

Hi @Rajesh Konda Short answer: this may not be possible with an automation rule. To learn why, please continue reading... Longer answer: Your solution approach is apparently copying comments from one issue to its linked issues. Assuming the creation of new comments is working, the challenge is updating the comments in the…

Would you please post an image of your current complete rule and of the edit issue action? The format jiraDate should match what the error shows: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- UPDATE: I forgot that because the Advanced Roadmap fields are not fully…

Hi @James Carnes-Dela Cruz Although it is great to add to existing suggestions, your question seems a variation of this one. And so I recommend creating a new question next time; that will help focus the conversation on one question at a time to get to solutions faster. Thanks! For your need, and without seeing your rule…

Thanks for that information. There are some missing curly brackets in your JSON, an extra comma, and the date is in the incorrect format. To set that field it must be in jiraDate format: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Date-picker-custom-field { "fields": {…

Awesome; I am glad to learn that helped!

@NC -- I will respond in that other thread as this is a new question.

Hi @NC Looking at the rule image from your other post here: https://community.atlassian.com/t5/Jira-Software-questions/Re-Re-automation-Add-fix-version-to-existing-fix-versi/qaq-p/2608692/comment-id/921557#M921557 By default, actions in rules use the values of the issues based on time-of-load. And so your second edit may…

Hi @Amer Jneid 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.…

Hi @Erika Reategui As you have solved this yourself, perhaps post what the cause was, the solution, and then mark your own response as "answered" for the question. That may help others who see a similar symptom in the future. Thanks! Kind regards, Bill

Hi @Samuel Jobin-Morissette -- 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…

Hello, all! Short version: I believe there is problem with the first Send Web Request action inside of the branch. This could be validated by: reviewing the action for errors; or copying the rule, removing all branching, and explicitly only trying to update any form except the first one (such as by saving the second id…