Bill Sheboy Expert

Hi @Casey Enderlein You may actually want multiple rules for a scenario to copy a field from the parent to a child issue. For example: * When a child issue is created, and has a parent with the field set, copy the field to the child issue * When a child issue edits its parent, and has a new parent with the field set, copy…

Hi @Todd Skelton The current date / time function is {{now}} and not {{now()}} and your date increment is missing the units of measure, such as plusDays() Please look here for examples of the syntax to increment a date / time…

Hi @Yaniv First, there are typographical errors in your smart values for {{lookupIssues}} references. Smart values are name, spacing, and case-sensitive. Incorrect values are returned as null. Next, that error message tells you the values are in the incorrect format, and must be passed exactly as "yyyy-MM-dd" but passing…

If your Jira Site Admin cannot identify the cause of the differences, perhaps ask them to submit a support ticket to ask the Atlassian team: https://support.atlassian.com/contact/#/ You appear to be on a paid license and so your admin can create the ticket. When you hear back from them, please post what you learn.

For the only underlining I see in that text I would expect it to work...at least for issue import. Does the target field have markup formatting for the field editor? Perhaps check with your Jira Site Admin on the field configuration.

Yes, it did. Here is an example CSV that worked to underline multiple words: type,summary,description Story,"hello, world",here is some text +to be underlined+ in my description

Where are you trying to enter that formatting? With the "new issue view" editor, the field controls support adding things like underline, not by manual entry. I updated a Description field using both an issue import from CSV and an automation rule and the formatting worked as expected.

Hi @Raghu Kiran Kumbakonam Shrinivasa [EXT] -- Welcome to the Atlassian Community! What type of project are you using: company-managed or team-managed? If you are using company-managed, you could use the card color feature to add a stripe of color to the carried-over stories. For example: * from the board, navigate to ...…

Hi @Mark Kraska Have you tried surrounding the entire text with the plus-sign for underlining? For example: how would you underline: +"this is what should be underlined"+ https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=texteffects Kind regards, Bill

Thanks for that information, and... When you describe it does not work consistently, have you checked the following: * Are the types of the fields all numeric? * Do the fields all have numeric values? * Have you confirmed the smart values are correct for the fields? Please use this how-to article to do…

Hi @TP As Trudy described, that variable cannot be re-declared to update it, or to update it sequentially. For this type of scenario, there is a workaround for the parallel processing of branches using variables, and it requires some assumptions: * you have fewer than 100 items in that branch * you are willing to rename…

Hi @Ken Parry Do you mean in the automation rule editor? If so, the individual conditions and their actions may be duplicated by selecting the "Duplicate" option by hovering over the top-right of the condition and selecting the option. However, I do not believe the entire if / else block with all conditions and actions can…

Hi @Garry Broughton Jr. -- Welcome to the Atlassian Community! If you can write a JQL query based on your date / time field and criteria to identify the issues to update, a rule could use that JQL in a scheduled trigger. For example: project = yourProject AND yourDateTimeField > 5h In this case, the "5h" is relative to the…

Hi @Sara Valoti SK For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @sacha_rouzkhosh Would you please post an image of the audit log details showing the rule execution? That may help provide context for what is happening. Thanks! Kind regards, Bill

Hi @Mohamed M_ El-Zalabany -- Welcome to the Atlassian Community! The issue types (and other configurations) for a team-managed project are unique for each project. As you saw in the audit log, the issue type conditions were not met. This is because they used the id value for the issue types when the rule was created and…

Hi @Mircea Craciun If you add up the remaining estimate values for that user, it matches the chart value of 1w 7h 30m. A "week" is 5 days for that sum. Kind regards, Bill

Thanks for trying that. This symptom is caused because the Start Date and Due Date are date type, but that function appears to only work with date / time types. A workaround is to format the values as jiraDate text and then convert back to date / time types: {{#lookupIssues}} {{#last}} start date:…

Hi @VolodymyrYu -- Welcome to the Atlassian Community! What version of Jira are you using: Cloud, Server, or Data Center? If you try those epoch value functions with a single issue, what do you observe? For example: {{#issue.created}}format="toMillis"{{/}} Kind regards, Bill

What did not work as expected? Please provide examples of the exact scenarios you tried for context. Also, please post an image of your complete, updated rule and the audit log details showing the rule execution. Until we see those... It is possible this is the difference in time zones. I believe values such as {{now}}…

Well done! One of the challenges with splitting some text is ensuring the joining delimiter is a known string of text. The default appears to be comma-followed-by-a-space: ", ". That seems consistently used for lists but not arrays. What you did by explicitly adding the join(",") helps to confirm what to split() on later.

Please try to stay with one thread when responding. That will help others reading this question in the future know if there are multiple solution approaches. Thanks! When you created the variable, that is stored as text. It is no longer a list. Please try this to parse your saved variable by converting it back into a list:…

First thing, as you are already referencing the custom field by its ID value, I recommend just hard-coding the field name. That will be much simpler and more efficient for an email action. Regarding how to do this with the REST API instead... * Using a Send Web Request action, the rule will call the REST API to get the…

Hi @Tomas Franco -- Welcome to the Atlassian Community! Without seeing your actual rule or calculations... Yes, math and logic operations may be combined n automation rules. Your scenarios specifics, and how you want to use the results, may determine what is possible. For example, expressions like these are possible:…

Thank you for clarifying, Mike. Perhaps there is something broken with the Jira site or specific project configuration that is impacting the reporting. As you appear to be on a Standard Jira License level, your Jira site admin can submit a ticket to the Atlassian Support Team. They may see something in the project or site…

Hi @Sushmita Chakraborty Yes, that is possible. It may be done in two rules, or possibly one rule if you have fewer than 100 issues in the epic's child issues and their subtasks. You may want additional rules to handle edge cases, such as someone manually editing the automatically-set label value. What have you tried thus…

Hi @Digvijay Singh Gehlot and @Trudy P Claspill This smart value is documented as working for Jira Cloud and Server / Data Center, and here is the open defect for it not working for Cloud: https://jira.atlassian.com/browse/AUTO-1069 Looking at the REST API for Cloud, it appears the names are only returned when the…

The smart value you want is fixVersions (noting that is plural): https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.fixVersions-- To set that field to the list of named versions from the trigger issue, please use this: {{triggerIssue.fixVersions.name}} If that does not work, please post…

Please review that other post, as it outlines what is needed to sync this field between the projects, including: * adding the custom fields to the JPD project * making the rule global, or multiple-project in scope * accessing the issues by the links, such as "implements" and "is implemented by" depending upon the direction…

 @Adrian Avalos -- No, there is nothing built-in for time in status smart values. For out-of-the-box features, process time measures for things like the built-in control chart are likely computed just-in-time from the issue history data. I do not believe they are in any fields or smart values that customers can access. It…