Bill Sheboy Expert

Hi @Vinícius Pereira You could add the ROUND() function around the value, selecting the desired precision: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/#Functions For example, to round to 3 decimal places: {{#=}}ROUND(({{issue.customfield_10397|0}} + {{issue.customfield_10398|0}})…

Hi @Conor McCarthy -- Welcome to the Atlassian Community! Have you tried from the user management / permissions settings: project settings > access That will also reveal if there is already a third creator (such as from someone added from a Site Admin role). Kind regards, Bill

Hi @Michael Goldberg What you describe seems to be an overlap between the "fuzzy" and "prefix and suffix" searches with the JQL CONTAINS ~ operator: https://confluence.atlassian.com/jirasoftwareserver/search-syntax-for-text-fields-939938747.html#Searchsyntaxfortextfields-fuzzyFuzzysearches:~ I have not found specific…

Hi @Mark Farmer -- Welcome to the Atlassian Community! What is the scope of your rule: single-project, multiple-project, or global? A single-project scope rule can create / clone issues into other projects, but it cannot access them in any other way. That is likely why no linked issues are found in your rule condition.…

Hi @Jaap Francke -- Welcome to the Atlassian Community! There is nothing built-in to dynamically lookup that information (other than for issue keys and issue lists). A workaround for your scenario would be to use automation rules to update the Description field when the other fields change. This can be a brittle solution…

Hi @Mateusz Krawczyk -- Welcome to the Atlassian Community! What is your relationship to the product vendor you are recommending? When recommending a product, disclose in the post any relationship you have to the vendor. To learn more, please see the guidelines:…

Hi @Nicola Zerbini -- Welcome to the Atlassian Community! What problem are you trying to solve with this rule? That is, "why do this?" Knowing that will help the community provide better suggestions. Until we know that... Please post images of: * the audit log details showing the rule execution * the Manual Trigger's…

Hi @Raimi MÖLLER -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have a rule that is not working as expected, please post the following to provide more context: * what type of project is this (e.g., company-managed, team-managed, etc.), * what type of field are you trying to…

Hi @Olivier GIRAULT From my perspective, JPD is based upon team-managed projects (TMP), and thus you are correct: many of the project-specific, custom fields are unique for each project. There are several ways to mitigate those differences: * The simplest is to only use one JPD project. If the JPD project is your…

Hi @Megharaja_Chandrappa_appserve_ai This is a duplicate of your earlier article: https://community.atlassian.com/t5/App-Central-articles/Supercharge-Jira-with-Enhanced-User-Profiles-Smarter-Faster/ba-p/2941312 Please delete this one or ask the community managers to do so. Kind regards, Bill

Hi @Hais_ Pedro -- Welcome to the Atlassian Community! Your rule is using the Smart Values Condition, and so at least the first value should be a smart value. Please change your condition to check the comment body: * smart values condition:* first value: {{comment.body}} * condition: contains * second value: finalizado no…

Hi @Martin Karlsson Short answer: what you are trying may not work because of known defects with the reliability of the Fix Versions field and the changelog available to automation rules. If you still want to try this... Advanced Branches take a list as a source value, but the value you are supplying is a text string. You…

Hi @Valerie Knapp I respectfully suggest not using Created Variables with the same name as other smart values. There is too much risk of a person making an error or the rule interpreting the value incorrectly. When I create variables, I always add a prefix to avoid such collisions, such as varEpicSummary. Kind regards, Bill

Hi @Sabina Alistar -- Welcome to the Atlassian Community! You are correct: there is no way to add additional fields to the view to work like the built-in ones. Have you tried using the Issues list view (from the left side of the page) with the Basic option, as that would be similar to what you asked? That would be easier…

Hi @MJJALP -- Welcome to the Atlassian Community! You have already asked this question as part of the conversation for this other one you asked 4 hours earlier: https://community.atlassian.com/t5/Jira-questions/Team-Managed-Project-Issue-on-Story-Points/qaq-p/2940887 Please stay with one thread to help focus the responses…

Hi @Christopher Mundt -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image for continuity, * images…

Hi @Erin Lee Short answer: I hypothesize that is not easily possible, and it may be simpler to investigate marketplace apps for issue cloning which can support copying that formatting. Since such formatting, including the relatively new "action items" were added, there have been many community posts that copying the…

Hi @Tanna Walters I agree: in my opinion, that seems like another experimental feature to support some niche set of customers, and probably should have been disabled by default (as should most such experiments). I have experiments / lab features disabled for my profile and the feature still displays for me, so it appears…

Hi @Ashleigh Hamilton I recall a related problem from last week with filters for the "none" cases of other fields on Ideas. You may want to work with your Jira Site Admin to contact the support team to learn if that same symptom impacts the Assignee field: https://support.atlassian.com/contact/#/ Kind regards, Bill

Hi @MJJALP -- Welcome to the Atlassian Community! Adding to Trudy's suggestions: Although Team-managed projects use the "Story Point Estimate" field, it is not consistently called that in the UX. For example, in the Project Settings where you checked for the estimation type, it is just called "Story Points". On the issue…

That depends upon the field type as replace() takes text.

Hi @Vitor Hugo Campos Lage -- Welcome to the Atlassian Community! 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…

Hi @Danielle Drapeau -- Welcome to the Atlassian Community! Adding to John's suggestions: The replace() function takes two text strings as parameters, but you are passing the Due Date directly (which is a date / time represented as a number). Please try updating that to use the format you want as a text string. For…

Thank you for checking with the single edit. If there are no duplicate fields (with those names) and the fields can be edited manually from an issue view, I am unclear why those errors would appear. I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support to check. They have access to logging /…

Hi @Aiste Marija Aidukaite-Urbanovic -- Welcome to the Atlassian Community! To copy the field from the parent, use that option in the edit: "Copy from parent". That will use the built-in parent / child relationship for issues. For example, between and Epic and Story. However what you show is "issue linking" and not the…

Congratulations and well done, @Esther Strom 

Hi @James Walters It appears that symptom was just logged today as a defect in the public backlog. Please watch / vote for it to see any progress: https://jira.atlassian.com/browse/JRACLOUD-93055 Kind regards, Bill

Thank you for the additional information, @Rita Arellano You describe using multiple automation rules (beyond the scope of this question) to update version fields, and precise manual field changes, relying on people doing them in the correct order...with no rule update collisions. For example, your answer to my first…

Hi @Carlos Pi -- Welcome to the Atlassian Community! Short answer: I believe the only way to detect adding a "delivery ticket" issue link to a JPD Idea is using a broader-scoped rule: multiple-project or global scope. This will detect it from the software project side, allowing branching to the Idea for access and updates…

Hi @Rita Arellano First, here are some questions to help clarify your scenario, particularly to learn if this is to add versions or to synch versions between the Epic and Story issues. I recommend pausing to discuss your scenario with another team member; explaining it will help clarify the problem / solution approach for…