Bill Sheboy Expert

Interesting, as those should be the same format to allow the copying directly. Let's try JSON again, forcing the format to exactly what is needed...however, we will first extract and pre-calculate the expression as variables to exclude any possible timing / racetrack errors for the evaluation: * action: create variable*…

Awesome, and well done! Please note my earlier note about the results coming back with this approach. Theoretically, {{issue.worklogs}} could contain up to 5000 entries, although I doubt that actually happens in a rule! (Everything else for rule data-loads has a 100 item limit.) And so if you have over 100 worklogs for an…

Thanks for that info, @Betany Riley Would you please post the complete smart value expression used to update that date field? Also, is the PRD Start Date (JIRA) field a date-picker field type, configured in the global (i.e., company managed) settings?

Hi @Jit -- Welcome to the Atlassian Community! Adding to Valerie's suggestions: Automation rules trigger after an event has happened, and so they cannot show a screen / view. Instead a workflow validator would be needed to gather / check the required field information. Kind regards, Bill

Thanks for that info! With that, you could try something like this: * trigger: issue transitioned * action: create lookup table* name: varMatchTextToLabels * row* key: printing * value: (print|printing|printer) * row* key: gratuity * value: (gratuity|gratuities|grat) * ... * action: create variable, to convert the summary…

Hmmm...the "raw" field values of {{from}} and {{to}} appear not to be working for that field type...or they contain other metadata which prevents the math. Let's use a math expression with the string values in the Create Variable action: {{#=}}{{#changelog.WorkDuration}}{{toString}} - {{fromString}}{{/}}{{/}}

Hi @Лёня Криволапов It seems you are duplicating your question from here: https://community.atlassian.com/t5/Automation-questions/Need-help-calculating-time-in-each-status/qaq-p/2934650 Kind regards, Bill

Hi @Chris Shernaman For more Atlassian-related sources, please see these: * Weekly release blog: https://confluence.atlassian.com/cloud/blog * Status pages (to watch for outages / releases): https://status.atlassian.com/ * Security…

Hi @Katelyn Melanson Would you please clarify what you are trying to do? Perhaps if you post images of your complete rule and audit log details, that will provide some context. For fields which support mentions, such as Comments and Description, that looks like this behind the scenes, where the user's account ID value is…

Hi @Candelaria Pereira -- Welcome to the Atlassian Community. What is the source of the content you posted? If this is from an automated / bot source, please review the community guidelines regarding disclosure of such sources in the text of your post:…

Hi @Jorge -- Welcome to the Atlassian Community! The symptom you are seeing is likely a timing, or racetrack, error in the rule: * the Edit Issue action, when using JSON, can try to parse the JSON before it has been fully evaluated, and * the looking up of the asset data takes time...regardless of how / where it is used in…

Hi @Felix Köhn There is an intermittent defect for this symptom for Jira Cloud, where variables cannot be consistently used to increment date / time values...even when converted with asNumber. I do not know if this defect also applies for Server / Data Center automation, but you could try two workarounds:…

Hi @Лёня Криволапов Rather than manually building that human-readable expression, please use the diff() function with the prettyPrint format: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference--- For example: {{issue.some start datetime.diff(issue.some end…

Hi @Paka -- 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, * images of any relevant actions /…

Hi @박예담 -- 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 images of the rule, edit issue action, the audit log details, and explain what is not working as expected. Those will provide context for the community to offer…

Hi @Nur Fatin Adding to Stephen's suggestions, both of the methods he noted work. I just re-tested to confirm them. For example in the message: URL only: {{issue.url}} As hyperlink syntax: <{{issue.url}}|This link is for {{issue.key}}> If those do not work for you, please post some images for context: * your complete rule,…

Hi @arkadiusz_Niewiadomski Is your customfield_10216 field a user field? If so, is it single or multiple-selection? As you have written the smart value expression, that will only work for a single-select, user field. Next, have you confirmed the custom field contains a value (i.e., a selected user), perhaps by writing it…

Hi @Betany Riley First, I recommend writing that smart value expression to the audit log, using the Log action. That will help diagnose rules like this. Next, your rule is trying to update an issue in a different project, and I hypothesize your rule has a single-project scope in the details at the top of the rule. The…

Hi @Christy Kennedy In the documentation for that marketplace addon, there are many automation rule examples. Here is one similar to your scenario, using a regular expression go determine if a specific item is completed: https://docs.herocoders.com/checklist/add-label-when-a-given-checklist-item-completed That example…

No worries; we are all learning as we experiment with rule-writing. You may use the Log action to write results to help with debugging, which I see you already have used in your rule. For example I recommend writing these to the log for your rule to observe what they contain: WorkDuration from and to String:…

Thanks for that information, @Natalie Franklin FYI -- Please try to stay within one thread when responding. That will help others reading this question in the future know if there are multiple ways to solve it. Thanks! Back to your question... You show multiple ways to get the issue needed, so let's assume the rule trigger…

The diff() function is for date / time values. Please try using a math expression with those changelog values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/

In my opinion, this still depends upon how your teams manage feature development. For example, if you build features incrementally, where some capabilities can be initially released to customers and improved with later releases using customer feedback, a team could use multiple releases. If instead there is no increment,…

Hi @Ann Rumenapp Assuming your WorkDuration field smart value is correct, please try this one, fixing some case errors and removing the "days" from the end: {{issue.Start date.plusDays(issue.WorkDuration)}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-plus-unit--- If that does…

Hi @Ashley Honeycutt Your rule could make a change to a custom field, such as a text field, noting the most recent execution, and that would appear in the issue's history. To do both the paths you describe (sent the message or did not send the message), the rule would use an if / else block to handle both. Kind regards,…

Hi @Harish Narayan Subash -- Welcome to the Atlassian Community! It is unclear to what you are referring... * If you mean "can a version / release value in the Jira Fix Versions field contain multiple issues", the answer is yes. * If you mean "can my software team put multiple features in our code releases", the answer…

Hi @Shikhar Madan -- Welcome to the Atlassian Community! I am unclear which date you are trying to use. You could use the automation date / time function to subtract the value needed: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-minus-unit--- If that does not help, for a…

Please post an image of your complete rule (in one single image) and an image showing the complete edit issue action where the field change is attempted.

Hi @Molly -- Welcome to the Atlassian Community! First thing, bulk, text-pattern replacement in automation rules can be challenging, primarily due to the possibility of collisions during issue updates. Next, please use caution with regular expressions and automation rules. There is no documentation on what is (or is not)…

Hi @Nadege You appear to be extracting issue keys from a comment body. There are several things to handle for that scenario: First, the match() function can have difficulty with comment formatting, such as newlines. Thus it makes sense to parse those out first, perhaps by using the replace function to convert them to…