Bill Sheboy Expert

With the announcement of Atlassian laying off 10% of staff apparently due to AI-tool impacts, my hope is there is limited impact upon the excellent people supporting all of us in the community.

Hi @Aaron Matthys First thing, I am just another Jira customer and have no specific knowledge of what the Atlassian teams are doing. With that out of the way... None of the Jira Product Discovery (JPD) suggestions and defects have been in JAC as a public-viewable project since JPD was released; it was not removed from JAC.…

Thanks for that information, @Evert Morren Atlas Admin -- And FYI, it often helps to seen an entire rule and audit log for context diagnosing symptoms. Let's assume you just want the text from the comment and are willing to ignore any formatting, links, etc. In that case, please add the text function at the end:…

Hi @LeanZero SRL As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording, and not just in your profile name / badge. For more information, please see: Atlassian Partners - Rules of Engagement…

I wonder if one could get the on-call responder with the REST API endpoints using the Send Web Request action, and then use another endpoint, or a JSON expression with an edit work item action, to set the Assignee.

To send one email per assignee, please see the article I noted earlier: https://support.atlassian.com/automation/kb/automation-rule-to-send-single-email-for-all-issues-per-assignee-due-next/ With that approach: * the scheduled trigger has no JQL * instead, a Lookup Work Items action uses the JQL to identify any items and…

Hi Community Champions / Managers, This JPD question appears to have been mistakenly posted in the automation area. Please move it to the JPD Q&A one. Thank you! Kind regards, Bill

Thanks for those images, @mgupta Based on what I see in the rule details, I wonder: are you using a service account for the rule? And, related to the scheduled trigger: * The trigger does not have any JQL to provide work items to the rule* The option "Run a JQL search..." is not enabled * Instead, there appears to be a…

Hi @mgupta For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule execution * explain what…

Thanks for that information, @Tami King There are several global fields (and some field types) which cannot be added to JPD spaces at this time, and it appears Sprint is one of them. One possible workaround is using a custom field in JPD to "roll up" your Sprint value from the linked, delivery tickets with an automation…

Hi @Derek Fields _RightStar_ Yup, I remember when they removed that permission for the AUTO project in JAC. I believe it happened at the same time as when they hid the old Code Barrel backlog, blog, etc. Oh well... There is a related open suggestion for using a smart value the assign action:…

Hi @Evert Morren Atlas Admin For a question like this, context is important for the community to help. Please post the following: * an image of your complete automation rule in a single image for continuity * images of any relevant actions / conditions / branches * an image of the audit log details showing the rule…

Hi @AnthonioD Yes, and...to the suggestions from @Florian Bonniec Please consider there are many cases to handle a field synch between parent / child work items. Based upon the level of accuracy and frequency of updates, this will require one-to-many automation rules. To learn more, please see this article I wrote on field…

Hi @Tijs Vrolix As you are likely on a paid license using Rovo and other Atlassian products, I recommend working with your Product Admin to submit this question directly to Atlassian Support here: https://support.atlassian.com/contact#/ Based upon the Acceptable Use Policy, there are several things under the section…

Hi @Juan Carlos Pin When you have completed some badge / kudos-related thing and waited a reasonable amount of time for it to appear, consider posting to ask about it on the Forums bug report thread. What you are observing could be from a one-off situation or a larger-impacting thing, so checking that page and the status…

Hi @Tami King Where are you trying to see the Sprint field in in Jira Product Discovery (JPD)? JPD spaces contain Ideas, and those spaces do not have Sprints. There could be "delivery tickets" linked to an Idea, and those delivery tickets could be in a software project which is using a Scrum board and sprints. Kind…

Hi @Erika Reategui Yes, and...to the suggestions from @Mikael Sandberg and @John Funk An if / else condition block will help when you expect only one of the values in the Labels: A or B. However, there is no built-in restriction to prevent someone entering both Label values, A and B. What do you want to happen in that…

Hi @Alex Gerulaitis First thing, I am just another Jira user and thus have no specific knowledge of the internal decision-making of Atlassian. With that out of the way... In my opinion, this boils down to: personas, experimentation, and license levels...relative to what problem / purpose a customer team is trying to solve…

Thanks for that information, @Sébastien OZANNE When the sprint changes for the work item, the Field Value Changed trigger can be used. And, the {{changelog}} smart value may be used to find previous values: * the fromString value will have the sprint name * the from value will have the sprint id To get the removed sprint's…

Hi @Chad Henderson Yes, and...to the suggestions from @Mikael Sandberg I see two things to change in your rule before you continue testing, and they may help address this symptom. First, the Work Item Created trigger has known racetrack timing problems. That is, the rule can start running before all of the data is…

Hi @Sébastien OZANNE The Field Value Changed trigger on the Sprint field detects changes to any Sprints associated to the work item. It does not detect changes to the Sprint's attributes: Name, Start Date, etc. as they are not stored with the issue; only the Sprint id is stored, and the other data is looked up when needed.…

Hi @SianS Yes, and...to the suggestions from @Trudy P Claspill and @Brant Schroeder I recommend never using conditions directly on triggers; instead add conditions after the trigger. For your specific scenario, try adding all possible conditions to the JQL to simplify the checks, such as checking the assignee is not empty.…

Hi @Henrique Bittencourt Yes, and...to the suggestions from @Chris Rainey -- Although automation rule triggers use events to detect when to start, and work item event documentation indicates: An event with the name avi:jira:updated:issue is sent when any field on an issue is modified... That is not always the case. As…

My understanding is: Atlassian knows about the racetrack timing defects, acknowledges this will take architectural changes to fix, and provides no timeline when that will happen. That was their response when I noted the symptoms with the release of conditions on triggers. For some rule triggers, adding a condition on work…

Hi @Graeme Wright Without seeing the specifics of your complete rule and audit log details for context... I wonder if you have a condition in the trigger, and that is producing inconsistent results because of the known racetrack timing problems in some rule triggers. That is, the event fires which triggers the rule before…

Hi @Ramya R -- Welcome to the Atlassian Community! Without seeing your entire rule and audit log for context... Please note we have no idea what the audit log renderer does; that behavior is undocumented. Thus, the log entry adder could be performing various text formatting and type conversions to display plain text in the…

Hi @Jose Henrique Polidori -- Welcome to the Atlassian Community! Without seeing the specifics of your automation rule, I expect what you describe is possible. The rule could use a Work Item Created trigger, and then select the correct endpoint in several ways: conditions, a lookup table, or an inline conditional…

Sorry, I misunderstood your question, @Susan Waldrip Yes, you may get the selected items by iterating over the custom field. For example, to get the names of the selected options, please try this: {{issue.customfield_12345.value}} That will produce a list of values with comma-space separators. If you wanted bulleted items,…

Hi @Susan Waldrip To get all the possible values for the multiple-select option field, the rule could call the REST API endpoint using the Send Web Request action to do so.…

Hi @John Funk No, I have not done that yet. Instead...I created this discussion to learn if I was missing something and that tracking had a status page elsewhere, or if people had other suggestions to improve the idea. Thanks!