Bill Sheboy Expert

Hi @Sowmya For a question like this, context is important for the community to help. Please post the following: * what version of Jira are you using: Cloud, Server, or Data Center * for Cloud, what type of project is this: company-managed, team-managed, JPD, etc. * an image of your complete automation rule in a single…

Hi @Tanguy Crusson Thanks to you and the team for the continuing addition of great features to JPD! A couple of quick questions / FYIs: * For the "More control over who can do what" I believe the granular permissions applies to all license levels, but the locked filters is for Premium only. Is that correct? * The link you…

Hi @Olga Springer Is this a premium license level only feature? If so, please add that to the top of the post for context. Thank you! Update: please disregard my question as Tanguy pointed out this is a Contributor view feature. Kind regards, Bill

Hi @s_gridnevskii Have you tried saving the source JSON with the Create Variable action as that will force it to plain text (i.e., no objects recognized) and then use the variable in your other action? Kind regards, Bill

Hi @Pallavi Shirodkar Only customers on a paid license level can submit a ticket to Atlassian Support, and @Patrick Sumariva is asking about a Free license level. Additionally, even for a paid license level, only a Org or Product Admin user can submit tickets for paid license accounts. Kind regards, Bill

Hi @marc -Collabello--Phase Locked- Agreed; it is marketing the product(s), and... This content was originally posted as a "question" in the Jira area. The community managers moved it here to App Central to reflect the marketing aspects. Kind regards, Bill

Hi @Jim McGowen I recall some older defects describing inconsistent behavior with JQL, changelog-related operators like this, particularly for Team-managed project (TMP) status values. The workaround for those cases was to use the id values rather than the status names in the JQL expressions. Perhaps try that to observe if…

Hi @KC Wong I agree; the UX changes from a couple of years ago to "hide" the audit log make it more difficult to manage, develop, and debug rules. One wonders if Atlassian did this to solve the scrolling and state-management problem of the rule being different than what is currently shown in the log...but that was always…

Hi @Denis Paul Thanks for your article. Yes, and... One of the root causes of symptoms you describe is when Team-managed projects (TMP) were added with the People type field, several of the attributes such as emailAddress were not available to automation rules. Here is one of the defects in JAC for…

Hi @Andrew Coutermarsh Based upon your response to the questions from @John Funk you appear to need to use the REST API to create the work item in the other site...and you are already using Atlassian Document Format (ADF) as a text node to add the information. A couple of things to try as a prevention for the smart…

Hi, @Kristján Geir Mathiesen In my opinion... On the positive-impacting side, I agree with you @Kristján Geir Mathiesen and others: the acquisition of CodeBarrel to integrate automation features without the need for addon apps was game-changing. My runner up would be the addition of Jira Product Discovery (JPD) and…

Hi @AKSHATA BIRADAR There is an open defect for intermittent display of attachment previews. It is shown as "waiting for release", so perhaps watch that one to observe any changes: https://jira.atlassian.com/browse/JRACLOUD-96330 There are other defects for attachments added using an automation rule, but those are a bit…

Thanks, @Tanguy Crusson !!

Hi @Mohammed Shakhib As the community clean-up project has started, please review the earlier announcement article to see some open questions / comments from the community on this effort. Thank you. Kind regards, Bill

Hi @flourish_x_yang What is the scope of your rule: single-project, multiple-projects, or global? With a single-project scope rule, the Clone Issue action can create issues in other projects, but I believe the linking happens afterwards and so perhaps is impacted by the rule scope. Thus, you can try two things: * Change…

Hi @Sonja Brown -- Welcome to the Atlassian Community! Yes, and...to the suggestions from @Trudy P Claspill In my opinion, Jira sub-tasks are one way to solve a specific team need: work breakdown. GIVEN we have a valuable item to deliver AND it is big enough we think about it in pieces WHEN working on delivering it THEN we…

Thanks for the additional information, @Arthur Smith FYI -- The two images posted (the rule and the audit log details) appear to be from different versions / updates to the rule as the Log statements do not align. Perhaps you made later changes to the rule and grabbed an earlier log entry? Looking at the incoming webhook…

Yes, testing the type is a good idea to confirm it is a "Reset Password" one. However, using two rules creates the need to test for all three other cases in one of the rules. This is why I suggested using one rule to test the single case (i.e., neither field contains UKG) and letting the Else handle the remainder. Having…

Thanks for finding that, @Trudy P Claspill -- I updated the post.

Thanks for clarifying the cases! I believe you can do this with one rule, using a single if / else condition block: * trigger: work item created * action: re-fetch work item data * if / else condition block, using the option for "All conditions match"* Work item fields condition: Description does not contain UKG * Work…

@Arthur Smith , this is a public, volunteer community forum where people collaborate to ask questions, learn from one another, etc. Thus it will help others if you post your rule information here for the community to help. If you are instead looking for one-on-one, dedicated support, please either: * contact your peer…

Thanks for those images, @Stephen Finegan First thing: there is a known, racetrack timing defect with the Work Item Created trigger, whereby the rule can start running before all the data is stable. This can cause errors and unpredictable results occasionally. The mitigations for that defect are: * Always add the Re-fetch…

Hi @Stephen Finegan I hypothesize the answer is, "yes, that is possible", although the community needs more specifics about your rule to know where / how to do so. Please post the following for more context: * an image of your complete rule in a single image for continuity * images of the trigger and any conditions used in…

Thanks for the images / information, @Snehal Singh and thanks for helping clarify the scenario, @Trudy P Claspill The general pattern of the rule you want is as below, using if / else blocks for each dependent Discovery type issue. * trigger: scheduled, with JQL to find relevant Epics * action: lookup issues, with JQL to…

Hi @flourish_x_yang As this is a very old thread, I recommend creating a new question with the "Ask a question" button at the top of the page. When you create your question, please remember to include the following for context: * what version of Jira are you using: Cloud, Server, or Data Center * an image of your complete…

Hi @Arthur Smith Posting the JSON for a rule is often not helpful for questions because: it can get truncated; does not match the spaces, types, etc. in other's sites, etc. Instead, please post the following for context: * what problem is your rule trying to solve; that is, "why do this?" * an image of your complete rule…

Hi @Alina Chyzh_Grandia Solutions 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…

Hi @Robert Condon Here is the open suggestion in JAC to allow the Teams REST API endpoints to work with a service account: https://jira.atlassian.com/browse/JRACLOUD-96410 Kind regards, Bill

Hi @Ant Farley This question seems related to your other one about filtering in ways JPD does not currently support. Please see my response to that one for ideas on a workaround:…

Hi @Ant Farley I do not believe that is possible yet. And, I do not see it on the JPD public roadmap: https://atlassian-product-managers.atlassian.net/jira/discovery/share/views/a0af4caf-5f1b-42be-8c57-24d1080122bc One possible workaround, depending upon your license level, is using a custom field and automation rules: *…