Bill Sheboy Expert

Hi @agnes BOURLON An automation rule triggers after an event has occurred, such as Issue Deleted, and thus: * a rule cannot prevent the deletion, as it has already occurred * the issue is now gone and some of its data may not be available after the deletion. When I tested with issue delete and a Jira Cloud rule, the…

Hi @Kumari dvipa Adding to Mark and Valerie's suggestions... You may have the incorrect smart value for your field. Smart values are name, spacing, and case-sensitive. And the smart value may not match the exact display name for a field on the issue views. When the wrong value is used, it will be replaced by null, often…

Hi @Mike Espitia As this is an older thread, I recommend creating a new question, and perhaps linking back to this one for context. That will help ensure more people see the question to offer suggestions. When you add the question, please include an image of your complete automation rule, images of any relevant actions /…

Hi @Lexi I believe your link to that old post is truncated. Is this the one you wanted? https://community.atlassian.com/t5/Jira-Software-questions/Increment-Custom-Field-on-Transition/qaq-p/1388215 If so, please post an image of your complete rule and the audit log details showing the rule execution; those will provide…

Sorry to learn that as many vendors are quite reliable. Perhaps look for another product which can do what you need.

Hi @Trudy P Claspill Good call, as there have been an increasing number of these for the last few days. There is a pending scheduled maintenance this weekend, 7 April, and so I wonder if something is updating earlier than planned: https://jira-software.status.atlassian.com/incidents/xckcr2snrjx0 Kind regards, Bill

Hi @Nelson Nittala You are using a marketplace addon to perform the issue / board colors, not a built-in feature of Jira, and the built-in board cannot do what you ask. Please contact the vendor of that product to learn what they suggest. Kind regards, Bill

Hi @Nikki Colletti Adding to Trudy's suggestions with some requests / questions... * When did you notice this error: immediately after creating and using the rule, or did it start happening recently after the rule was working successfully? * Would you please post images of both the audit log details showing the error and…

Hi @Varun_Sharma The created date of an issue is the date / time it was created. That is regardless of any source issue in the case of cloning. What you describe is not a defect; in fact, allowing other values would invalidate issue history if the created date could be arbitrarily set to another value. What problem are you…

Please try the branch on linked issues, selecting the link types needed. If you need to filter further on a field, add a rule condition. If that does not help, please post: * an image of your complete rule; * images of the trigger, actions, conditions, and branches; * an image of the audit log details showing the rule…

Hi @Jordan Bauman I believe the pie chart gadget's sort is based on the quantity, maximum to minimum. There are several open suggestions to improve dashboard gadgets, including their filter sort order, but I doubt any of those would be implemented. You may want to check the Atlassian Marketplace to learn if there are…

Hi @Lusine First thing, I am using Jira Cloud, not Jira Data Center, and so cannot test the suggestions I offer. They are based on what I know about automation rules, in general. With that out of the way... I believe there may be two ways to solve this. Let's check the easiest one first: Issues have the subtasks smart…

Hi @sharlaineu What do you want to happen if someone manually alters your ICE field, replacing the calculated value? If you want to set it back, consider adding that field to the trigger...or creating a separate rule for greater visibility of tampering. Kind regards, Bill

Hi @Sukpanitada Charoensup -- Welcome to the Atlassian Community! You are asking about the REST API for a vendor's product used as a marketplace addon to Jira Cloud. I recommend you check that vendor's documentation and / or contact their support team for assistance. Kind regards, Bill

Hi @Kelvin Teng -- Welcome to the Atlassian Community! In addition to the other answers provided... For automation rules, at least three things impact how to supply a value when the field is considered empty: * what is the state of the issue, such as immediately after issue-created / cloned * the field type, such as text,…

Thanks for that information. Please try this expression: ((1|2|3|5|8|13|21)(\.0))

First, and to help align on some Jira terminology: * an Issue is a work item in Jira; sometimes people refer to these as Cards or Tickets as some believe they have that appearance on a Board * a Board is a view of issues, based on some saved Filter * a Status is step in the workflow for an issue * on the board, there are…

Hi @Andrew Madar What does your customer mean by "stack the cards on the Board view"? What would that look like? Kind regards, Bill

When an issue has a direct link to another issue, either can be accessed by the links using the built-in features of JQL (and automation rules). You described Epics in one project are linked to Epics in another project, and so what I suggested should work. Are you instead trying to find issues which are not directly…

Hi @Rghiya From what you describe, I do not believe you need any extended JQL capabilities provided by the addon. Instead, a multiple-project scope automation rule could be triggered on a change to the field in one project, and then branch to the linked issues in the other project to make updates. Kind regards, Bill

Hi @Northern Kentucky Stargazers -- Welcome to the Atlassian Community! Without seeing your entire rule and the specific field-change the rule is triggered upon... * There are known problems with changelog accuracy for some list fields, such as Fix Version and Sprint for Jira Cloud. For…

Hi @Jamie Edmondson Depending on the number of recipients and the specifics of the email content for different recipients, this is possible with an automation rule. If the email varies by recipient and there were fewer than 100 recipients... * The list could be uploaded to an issue as an attachment file * An automation…

Hi @Catherine Huang -- Welcome to the Atlassian Community! Short answer: you may need a marketplace addon or custom built app to count those values for historical issues. More information... Based on your response to John Funk, it appears you already have a solution for counting changes in future transitions. For counting…

Hi @Ida Giersing 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 @Aron Kuch 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 @Nicola 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 @CTteam -- Welcome to the Atlassian Community! Adding to John's answer... To learn more about creating queries you need, please see this documentation and free training from Atlassian on JQL features: * https://support.atlassian.com/jira-software-cloud/docs/jql-operators/#CHANGED *…

Hi @Shahar Minkov Yes, I noticed that as well. It also now truncates column display when the field data does not fit. It seems the behavior changed when the new issue search was rolled out. And reverting back to the old search no longer has it, so the feature appears to have been removed in the last week or two. I…

Hi @Cash Coyne Without seeing your specific rule details... When you have the id for a single, select field option and want to set the value, please try advanced edit with JSON in the edit issue action: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Single-select-custom-field Kind…

Looking at that image, there appear to be extra curly brackets around the expression when you create the variable. Please remove those and re-test.