I created a rule from the library (When all sub-tasks are done → move parent to done) and used it as is, without modification - and it works.
The rule closes parent tickets when subtasks are done. To do so I creates transitions from all other workflow statuses to Done so that automation could perform the transition. Also, the transition uses a post-function to set the resolution value automatically.
So as I mentioned, the rule works - the transition takes place and the resolution value is set, but errors are appearing in the audit log for the automation rule. I have not been able to find an answer anywhere.
So in case anyone is asking why I am posting another similar question, while I have found similar problems in the community - this seems more common than I would have guessed - they are not the same set of circumstances, and also, none of the posts I found were resolved. I would love to know what's actually happening.
Hi @Rob Horan
One possible cause of this symptom is when using a team-managed project (formerly called next-gen) and the team has created a custom field which duplicates another field's name.
If this is a team-managed project, please check if there are 2 Resolution fields in the project.
It looks like it's not a major issue, but most likely there is a transition screen from the parent issue that needs to be filled out when you push it to done.
I would recommend the following:
1. Since you are using a post-function to set the resolution in the parent, remove the transition screen from the transition.
Sometimes, I find that Project Automation and Workflows post-function conflict with each other.
I suggest the following then:
1. Remove the post-function in the workflow and set the resolution in the automation.
2. I would also add a condition after the status trigger to check that this only applies to Sub-tasks.
Resolution is definitely missing from the edit screen. That would make it editable, wouldn't it? Resolution only appears on the resolution screen.
This project was fine until I added an automation rule.
This is just a standard Software project. Nothing special.
Thank you for replying though - I'm really confused here!
Hey @Matthew Knatz - Automation is not going to be able to call a transition screen. So you need to add another transition to the status being used in your automation rule and set the values that would be done through the screen. Then I would put a condition on the transition so that only the group atlassian-addons can execute it.
@Rob Horan - any update?
Hi everyone! Are you interested in beta testing Atlassian University’s newest (unreleased!) training course? We’re looking for 15-20 volunteers to test our newest training course, Basic reporting...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events