Bill Sheboy Expert

Hi @Devin Holland -- Welcome to the Atlassian Community! When performing date/time comparisons in automation rules using conditions, please check if the typing supports your intent. Specifically, using things like longTime lead to a text expression. And so the compare no longer has the benefits of a date/time type to help.…

Hi @Dave Symonds I suggest not editing the issue type with an automation rule, but instead perform a clone to the new type and then abandon (or delete) the original issue. Changing an issue type is a complicated operation that can run into problems due to differences of fields, workflow, parent/child relationships, etc.…

Hi @Nitin Gupte You could use the issue field changed trigger to start your rule, and then send the email. To get you started on creating your rule, please refer to these documentation and example sources: * https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation *…

Hi @Camon Jie I recall the last time I tried this it did not work with just the changelog. There are a couple of open defects for the changelog not working correctly for list fields like Sprint, Fix Version, etc. inside of automation rules. There are specific smart values for added / removed values from fields for…

Thanks for that information, Jason! Would you please explain...You describe copying these issues to the other project as their Due Date approaches. Why do that instead of just having a different board which filters on the date, keeping all issues in one project? For example, is this a security / visibility issue to limit…

Hi @Sanjivani Wayal I believe the timeSpent smart value is the human-readable one (e.g., 1h 15m) and timeSpentSeconds is the numeric one. Kind regards, Bill

When responding please try to stay with one thread. That will help others in the future reading this question to know if there are multiple solution approaches. Thanks! Next, your trigger is for any updates to Work Logged, and so that will not include new entries. Is that what you want? If you want all changes please…

Thanks for explaining the situation, and I expect you will not find a "one size fits all" answer. The different things you note require different capabilities / Jira features. If there was a simple way to roll those up together, Jira would already provide it. For example, if there was a single board to show JPD Ideas and…

I am confused by what you are posting: what is shown for log entry 6 (i.e., what I suggested) works as you asked to remove the outer quotation marks. And I just tested and it does remove embedded newlines as well. And...if you use the expression I suggested, there should be no need for the conditions so that will simplify…

In my experience, the implementation of match() in automation rules has trouble with newlines and regular expressions. And so a work-around for your scenario could be: replace the newlines with a token, perform the match, and swap the token back to newlines. For example:…

Hi @Matt Just to confirm, are you trying to remove only one leading and one trailing quotation mark, if they are present in your description field? If so, have you tried using the match() function with a regular expression to do that in one…

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

After a rule creates the issue, you have the smart value {{createdIssue}} to include any fields in the message: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--createdIssue-- One of those is the link to the…

After a I bit more testing I confirmed that with that button / action, it must take a different path through the move logic: only the "to" in the change log is set and not the "from". And so the remaining work-around would be to still use 2 rules: * created trigger, testing for a new subtask * issue field updated trigger…

Hi @Nicole_Brueckner For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Those will provide context for the community to offer ideas. Thanks! Until we see those... Are you…

Hi @Jackson -- Welcome to the Atlassian Community! For a question like this, please post images of your complete rule and the audit log details showing the rule execution. Those will provide context for the community to offer suggestions. Thanks! If you want to create just one issue, remove the JQL from your trigger. Are…

FYI to please try to keep to one thread when responding. That will help others looking at this question in the future know if there are multiple solution approaches. Thanks! Yes, I knew about that defect. And, I just tried converting a story to a sub-task (with a move operation) and it did trigger the issue updated event…

Hi @Umair Jabbar For the scenario you describe, I believe you may want two rules until you work out the details, and then you can experiment with one rule, using the Multiple Issue Events trigger. The challenge is your rule will need several conditions to handle the change of the issue type (or parent). What does your rule…

Hi @Nick de Palézieux There are known problems with automation rule parsing of the change log and list fields, particularly versions. Here are a couple of them: https://jira.atlassian.com/browse/JIRAAUTOSERVER-207 https://jira.atlassian.com/browse/JRACLOUD-81160 And so you may get a rule which appears to work, but its…

Hi @Luca Rasconi Is your board using Scrum or Kanban settings? Is this a company-managed or a team-managed project? You may find that information at the bottom-left side of the page expanding area. If this is a company-managed project, has the board's saved filter recently changed? If this is a team-managed project, when…

Hi @min -- Welcome to the Atlassian Community! The smart values are mostly listed on the documentation pages: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ To learn all supported smart values for your issues, please use the how-to article linked below. Smart values are name, spacing, and…

Hi @jiandong.luo Do you mean the lead time, or build cycle time for the issues? If so... That is not possible with the built-in dashboard gadgets. You could either investigate marketplace addon gadgets, or try using the Atlassian interpretation of a control chart. That control chart would allow seeing the measures and…

It appears to be collapsing / trimming after the newline. You may want to ping the Atlassian support team, or post this question in the Developer Community: https://community.developer.atlassian.com/

Thanks for that information, as it may explain the unexpected results you are observing... As you have shown, the JQL is the same for the trigger and the Lookup Issues action. What is the purpose of doing that lookup? What is the purpose / value of the timeStatus created variable? You mention a branch, but there is no…

Do you have Jira Service Management? According to the documentation, the internal attribute only works when that is installed. https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html

Hi @José Carlos De Oliveira Escalona What problem are you trying to solve by adding ideas from a Jira Product Discovery (JPD) project to another board? Putting JPD ideas on another board seems to invert the concept and value of using JPD, which is to perform highest level, portfolio management and planning. Often a JPD…

I am glad to learn that helped. For your other questions... I added a default value of 0 to handle the possibility that the issues have no value. Without that default, the sum would return a null value. For potential problems using story points in this manner... The default, built-in issue hierarchy for Jira is Epic >…

Thank you for that information. It is likely the smart value for the field is different than what you are using. Smart values are name, spacing, and case-sensitive...and they do not always match the displayed field name on the page views. Your field name has a hyphen, and so I expect the smart value is different. Please…

Hi @ANISH TANEJA 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 @Danno Adding on to the questions from Stefan... Does the scheduled trigger have JQL or is the rule only processing issues from the Lookup Issues result? If it is only processing issues from the Lookup Issues result, my assumption is the rule is using a branch to perform the update. When you post images of your complete…