Bill Sheboy Expert

Hi @Nita Brumbaugh The REST API endpoints only supports adding one link at a time and that is likely the cause of the limitation. I recall other posts where this how-to article on importing links with a CSV file for Jira Data Center also works for Jira Cloud. Perhaps give it a try:…

Hi @Andrey Ivanov What have you tried thus far to solve this? If you have started a rule and it is not working as expected, please note context is important for the community to help. Please post the following: * an image of your complete automation rule, * images of any relevant actions / conditions / branches, * an image…

Hi @Daniel Pfeffer For the multiple-select option field you show, the values have a digit in the first character. That could be extracted using the left() function. And then the list of values could be joined together for including in a math expression. For example: {{#=}} 0{{issue.myCustomField.value.left(1).join(" + ")}}…

Hi @Michel van de Wiel Please do not post bot-generated content without clearly indicating the source. For more information, see the community guidelines: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Kind regards, Bill

Hi @Michel van de Wiel Please do not post bot-generated content without clearly indicating the source. For more information, see the community guidelines: https://community.atlassian.com/t5/custom/page/page-id/rules-of-engagement Kind regards, Bill

Hi @Michel van de Wiel The smart values your rule references are the human-readable ones for time tracking. Instead, please try this to detect when the current total logged time is greater than the original estimate as number values: * smart value condition:* first value: {{issue.timetracking.timeSpentSeconds}} *…

Hi @Ste404 One way to do this would be using knowledge about the "start of epoch time", create a variable with that value, and then add the milliseconds to it: * action: create variable* name: varStartOfTime * smart value: {{now.withYear(1970).withDayOfYear(1).toDateTimeAtStartOfDay}} * ...something to get your Unix…

Hi @Darryl Lee Yikes! That is an interesting set of problems to solve the scenario. Here are some ideas, in no particular order (or guess of effectiveness ;^) * Is there any way to divide-and-conquer this so the check / label update is made when the page is updated by people, and then the only work for the 60-day schedule…

Hi @Silas Campbell -- Welcome to the Atlassian Community! You appear to be trying the format of if() function which has true / false values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#if That format is this: {{if(smartValue, "value if true", "value if false")}} Please note…

Hi @Shawn Doyle - ReleaseTEAM Anyone who writes an article may mark it as "Featured". It also appears community managers can mark existing article also. Kind regards, Bill

Hi @Sebastián Granizo -- Welcome to the Atlassian Community! That is an external tool, different from Jira's built-in features or marketplace apps. Please contact the vendor and their support team for help. If you need help to do that, please ask your Jira Site Admin to contact the vendor. Kind regards, Bill

You could manually look at the history for each issue, or you could use the REST API endpoint to check the issue history. Using the endpoint will require searching the results to find changes to the Description field and may require multiple calls with paging results if the issue has changed many times.

Hi @Zack Lane -- Welcome to the Atlassian Community! You are on the correct path, using functions such as startOfMonth() and endOfMonth(): https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#startOfMonth-- Those allow incrementing the value, such as with startOfMonth("+1") For example, for issues in your…

Hi @Muhammad Akram Sharifi What problem are you trying to solve? That is, "why do this"? Knowing that may help the community to offer alternative solution approaches. Until we know that... Do you want the last person who updated the Description field, or something else? If it is the last person, that could be one of two…

Yes, and...to what @Kelly Arrey suggested: Although it can be cumbersome, read all the way down in the automation documentation. Some things are quite well hidden, such as tips / tricks for using list iterators and the other example pages on smart value usage. I recommend re-reading those at least quarterly. Add community…

Hi @Aaron Eden Branches in rules which could-be-on-more-than-one-thing are executed in parallel and asynchronously, with no predictable processing order. With an automation rule, I know two ways to enforce issue creation order, but neither will work for your scenario of 25 child issues. * In-line, creating each issue one…

Hi @Ashish Bijlwan Would you please post an image of what you are observing? Are you the only person seeing this symptom or are your teammates also seeing it for the same issue? Kind regards, Bill

Hi @Ankathi.Madhuritha 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, * images of any relevant actions / conditions / branches, * an image of the…

Hi @Andrea Kolářová -- Welcome to the Atlassian Community! What problem are you trying to solve with this field and the two issues? That is, "why do this?" Knowing that may help the community to offer better suggestions. Until we know that... While you could use issue linking or JQL searches in automation rules to find the…

Greetings, community! In my experience, there are no best practices; there are only better or worse ones depending on the context of what helps a team at a point in time. For those wanting to better understand and apply use of the Scrum Framework, I recommend reading the current version of "The Scrum Guide" from the…

Hi @Monique vdB This guidelines article / thread now seems to significantly overlap the just-released guidance articles: * https://community.atlassian.com/t5/App-Central-articles/Atlassian-Partners-Rules-of-Engagement/ba-p/2899328 *…

For the value passed to the table's get() function, have you tried writing that to the audit log to confirm it contains exactly what you expected, and has no leading / trailing space characters?

Hi @John Erickson -- Welcome to the Atlassian Community! If that is a single-select, user field, please use the ... menu to the right of the field to select "Copy" and then select the field again to copy the value from the Reporter. Kind regards, Bill

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Thanks for that information. Please note checking the Updated field will check for all changes, and not just comments added. If this meets your needs, you have solved it yourself!

Awesome! One more recommendation... I recommend pausing, reading through this thread and your rule, and explaining it to another person. That will help solidify what helped in asking the question, the solution used, and tools to diagnose symptoms when rule-writing...and to share the knowledge with other teammates :^) Have…

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

Thanks, Josh. Perhaps try using \n instead, or concatenating on the newline: {{issue.customfield_99999.concat("\n")}} {{object.Notes}}

That is curious, as I am confident if that full expression may be used to add a label the variable's smart value could as well. I still recommend removing the Delay() action and adding Re-fetch Issue after the trigger and testing again. This symptom seems like a timing problem.

Progress! Let's try concatenating a newline after each value by updating that variable: {{#lookupIssues}} * {{customfield_12971.concat("\n")}} {{/}}