Bill Sheboy Expert

Hi @Jennifer Hart -- Welcome to the Atlassian Community! Would you please post the JQL you are trying to use? And...are you trying to filter on that other field or just display the values for the issues found? Kind regards, Bill

Hi @Shayan Ali -- Welcome to the Atlassian Community! I do not believe that is possible at this time. Please see this earlier question on this topic: https://community.atlassian.com/t5/Automation-questions/Send-chat-notifications-on-MS-teams-to-watcher-of-a-ticket/qaq-p/2293818 Kind regards, Bill

Hi @Gerald Oliver First thing: what problem are you trying to solve by doing this? That is, "why" do this? The built-in capabilities for ordering / re-ordering issues with the Rank field work well, although they do not provide a 1-to-N numbering. Back to your question... IMHO, a rule to handle a scenario like this is…

Correct; there is a separate rule action to do that: https://confluence.atlassian.com/automation/jira-automation-actions-993924834.html

There is a separate action to manage watchers. Do you see that one in your version of the automation rule editor?

Would you please post an example of the comment you are trying to parse? And, if you write both the un-parsed comment and the smart value expression driving the branch to the audit log before the branch, how do those compare to what you expected to see in the results?

Hi @Beth Shutt -- Welcome to the Atlassian Community! Some of the smaller teams I have helped have done this, using a user story format in the issue description, and one of the marketplace addons for checklist fields. They put the acceptance criteria in the checklists, allowing both one-place-to-look for information and…

As I described earlier, using automation rules requires learning and experimentation. We are all learning and so I encourage to take your time to understand how the rule works as you implement it. Perhaps pair with another team member to share knowledge and the work. That will help you both to maintain the rules in the…

The UI for the rule edit is not clear on this feature... * Rather than select the drop-down, type in the smart value * The value will appear below the field * When it does, select it with your mouse cursor * The smart value will then be used to set the field value.

Hi @Evelyn Ramberger That Issue Created trigger can fire so quickly that the issue's data is not yet available to the rule. And so the actions / conditions / branches do not work as expected. The work-around is to always adding the Re-fetch Issue action immediately after that trigger. It will slow the rule by about a…

Hi @Jerrod Van 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 @Talha Aras 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 @Abhishek Goyal You seem to keep asking this same question, with 3 questions thus far. Please wait until the community has answered your question. There is no need to repeatedly post it in different formats.…

Hi @Abhishek Goyal You would need two rules: one for new work logged (your current rule), and another to sum and log the earlier values. Once the second rule has added the earlier logging values, it may be disabled for future use. Regarding that second rule...As adding the individual logs for each issue could be…

Hi @Martijn Hoekstra Ignoring for now the idea of using story points rather than just time-based estimation... 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…

Hi @tech_tractorjunction -- 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…

Hi @Arun Unnikrishnan Adding to Fabio's answer: I would not recommend removing the prior sprint(s) when an issue is carried over; that is, not completed in one sprint and so continues in another. That would change the history of what happened, and takes away an opportunity for the team to consider what happened, learn from…

Which issue(s) are you trying to edit for the due date: the trigger issue or each linked issue?

There are definitely some stray / extra curly brackets in that JSON. Perhaps remove those. Next, smart values are name, spacing, and case-sensitive. And, smart values for a field in automation rules do not always match the displayed name on the Jira issue views. To confirm if a field is supported by rules, and what the…

Not that I am aware of: the key is generated when the issue is created.

Thanks for clarifying, Sarah. Unfortunately there is no public REST API to manage automation rules yet. Here are a couple of suggestions for that capability, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/AUTO-51 https://jira.atlassian.com/browse/JIRAAUTOSERVER-229 While we wait for that…

The re-fetch issue action must be outside and after the branch to reload the data for the trigger issue.

FYI -- Please reply to posts in the same thread rather than starting a new one. That will help people review this question to know if there are multiple solution approaches. Thanks! Your rule should not branch to the child issues, but instead should just use the lookup issues action to gather them to update the total.…

Rather than selecting Current Issue for the parent field, please type in the smart value for the key you want to use. When you do that, the key will appear below the field, and then it may be selected for use in the action.

That seems a variation on your question, as you now want to check for multiple, pre-defined summaries. For that case, I recommend doing these one by one to confirm presence of each issue before proceeding. Trying to do this in a loop may be possible, but seems like the behavior will be less predictable. Perhaps like this,…

When you branch to the linked issues, you are editing those linked issues, and not the newly created one. An alternative is to gather the linked issues using the Lookup Issues action with JQL, and then use their components to set the value: * trigger: issue created * action: re-fetch issue (When using the issue created…

Please post an image of the audit log details, showing the rule execution. You may do that with a screen capture tool, screen print, or browser addon to capture the image. And just to confirm, is the need to link the new story to the parent story of the trigger issue (subtask)? If so, please use a smart value instead of…

Oops, I missed that one @Jimmy Seddon Thanks!

Hi @Nic Ban -- Welcome to the Atlassian Community! The replace() function works with plain text replacement, and not a regular expression. Please try using replaceAll() instead: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#replace-String-target--String-replacement- Or better still, use…

Thanks again, @Jimmy Seddon for the updates! With the addition of the automation corner to this round-up... Next month please consider including the change to the automation packaging model (i.e., execution limits and scope) which took effect today, 1 November. It is quite an impactful change for customers.…