Bill Sheboy Expert

Hi @Jon Parker -- Welcome to the Atlassian Community! Is that other custom field a text field? If so, you may use the format() function with the layout needed: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-format--- Kind regards, Bill

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

Well done finding your own answer to that one! Using rules is all about learning and experimentation :^)

Hi, Alan! Perhaps look at an example work item with this symptom, checking its history and the automation log to determine if a rule caused the message. And if not, ask your Site Admin to submit a ticket to Atlassian support to take a look: https://support.atlassian.com/contact/#/

Please post an image of the audit log details for the rule execution, expanding all the areas at the right side. That may show why the rule did not update as expected. Also, did you confirm the rule scope is multiple-project or global? Otherwise that branch will not "see" the linked issues.

Hi @Jeffrey Bistrong and @John Funk There is a new defect just created for this symptom: https://jira.atlassian.com/browse/JRACLOUD-94687 Did your team create that one, Jeffrey? Kind regards, Bill

Thanks for that information. If one leaves the field it triggers as an update event. When your rule only needs both current values to proceed, try using a smart value condition to check both are non-empty: {{issue.customfield_12345.value}} {{issue.customfield_12345.child.value}}

Hi @Shai.Leib -- Welcome to the Atlassian Community! My understanding is the AI-generated summaries only work for Premium and Enterprise license levels when Atlassian Intelligence is enabled for the product, such as Confluence. Your admins may have turned off the feature so please check with them to confirm. Then the smart…

Hi @Davis, Jessica -- Welcome to the Atlassian Community! Other than the special Jira Product Discovery (JPD) link type used for Delivery work items, internally named "Polaris issue link", my understanding is the link types do nothing regarding work item relationships. That is, "blocks" does not block anything. Instead the…

Hi @Teplyashin Max That is not possible for the built-in Epic type in a team-managed project (TMP). Here is the very old suggestion to add that feature: https://jira.atlassian.com/browse/JRACLOUD-85704 I hypothesize that may not be implemented as the standard response to such TMP requests is "won't do...try switching to a…

Hi @Mohanraj Thangamuthu Here are two suggestions to improve your rule, increasing the chances it will work as expected: 1) The Work Item Created trigger (among others) has racetrack timing problems. That is, the rule can start running before all work item data is available to the rule. For your rule, this means the custom…

Hi @Shiwanshu Singh Smart values are name, spacing, and case-sensitive...and they often do not exactly match the field name displayed on the work item views. When an incorrect smart value is used, that returns as null, often failing silently in the rule. Please find an example work item with your fields and then use this…

Hi @Michelle Sullivan -- Welcome to the Atlassian Community! 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…

Hi @Antonia Short answer: that is possible with an automation rule and the REST API, and it may be unwise to do so. Work item types have different configurations for the project, work flow, fields, etc. And so changes from one type to another often need people to help. This is why Jira has a "Move" feature in the UX to…

Hi @Rohan Please review the community guidelines for disclosing sources when posting bot / AI-generated content: https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement Kind regards, Bill

Hi @Michelle S Just to confirm, are the fields you are using from advanced planning: Target Start and Target End? If so, I believe those fields are text (and not date) values when accessed in an automation rule, and so the min / max functions will not work. The fix is to convert them with the toDate function before the min…

Hi @Brian Kirwa When posting an apparently bot-generated answer, please note: * confirm the bot answer is valid; there are multiple errors in the above post * to comply with the community guidelines, disclose the source of the information: https://community.atlassian.com/forums/custom/page/page-id/rules-of-engagement Kind…

Hi @Paul Konen Before proceeding, would you please explain the problem you are trying to solve? That is, "why do this?" Knowing that may help identify other solution approaches. Until we know that... If I understand you question, I believe the answer is "no". When you need the previous values (e.g., from setting the…

Awesome; I am glad to learn that change solved it! 

You are correct: that functionality does not exist for the existing features. A workaround could be adding custom fields specifically to record deferred versions, etc. Before doing that I recommend pausing to discuss with the team: what would we do if we already had that information today? How would we act differently?…

Hi @Brendan Connelly -- Welcome to the Atlassian Community! Short answer: once inside of an iterator, no outside data is visible (such as the branch variable), and so the rule compares an unknown / null value, causing the equals function to fail. To fix this, let's correct a couple of things: You are essentially doing a…

For "deferred" you could just clear the Fix Version field until the work is built / scheduled for delivery. And...a Label value could be added to indicate the "deferred" state for tracking purposes.

Hi @Ofir Oxenberg Please provide the following for more context: * an image of your complete rule, shown in one single image for continuity * an image of the complete audit log details for the execution, with all of the areas at the right side of the log expanded Until we see those... When using the Lookup Issues action in…

Hi @Stefan Seefeld Jira work items have Fix Version and Affected Version fields. Have you tried using those to track when a work item will release, and for defects which current releases they impact? * https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Fix-version *…

Hi @Sebastian Pechhold First, there is no "jsonParse" function in automation rules. What is the source where you learned that function as it is incorrect? Some chat / bot perhaps? There is a jsonStringToObject() function that will help parsing the JPD date…

Hi @Marc -Devoteam- FYI -- Create Lookup Table has supported up to 200 rows since the last round of updates in July 2023. It is the pagination (when creating rows) that is limited to 20 at a time...making larger lookups more difficult to use in the editor.…

Hi @Gavin Steele What have you tried thus far to meet this need? If you have a rule that is not working as expected, please provide the following for context: * what is the type of your software project with the work items linked to the JPD Idea: company-managed or team-managed? * how many work items are linked to the…

Thank you for that rule image. With the Sprint Started trigger, please use the {{sprint.name}} smart value to access only that active sprint. Then in the Create Work Item action, type in that smart value in the Summary field: PMO Admin - {{sprint.name}} However, if you rule will use a different trigger, the expression…

Hi @Jens Schumacher - Released_so 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 about this, please see: Atlassian Partners - Rules of Engagement…

Hi @Andrés Gutiérrez Flores -- Welcome to the Atlassian Community! The date / time diff() function returns a text value in the selected units, such as hours. In your case, you are allowing it to use the absolute value format and then default to "prettyPrint" format to get "9 hours 30 minutes". But that value cannot be used…