Hello,
I have a simple rules to populate some of the fields when new item (task, story) is created.
It was working fine at first but now nothing happens.
In rule execution everything looks fine:
When I check logs it's ok:
In a task these fields remain empty. I'm working on next-gen project.
Hi @Katarzyna Michalik -- Welcome to the Atlassian Community!
For a question like this, please post an image of your rule and its settings to provide some context for the community to help. Thanks!
Best regards,
Bill
I have 3 rules which are constructed in the same way but for different fields.
I received notification from which I understood that my rule was working but then was overwritten?
Is it possible that having 3 similar rules can somehow interfere?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
When you have rules which could trigger each other, that can cause side-effects. If you have similar rules, perhaps not, unless the rules are acting on the same issues (e.g. task, story) and editing the same fields. Then the changes from one rule could replace the others.
I am curious: if you have 3 rules trigged by the same condition (issue created) to edit different fields, why not use one rule to edit all of the fields?
For your current rule, please consider adding at log statement after the trigger to record the {{issue.parent}} Perhaps the task doesn't have a parent.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I kept on adding new rules continuously and I thought that they will be triggered one by one, so there won't be a conflict. At first it worked fine. Anyway, I put all three into one, so now I have one rule to update 3 fields and it seems to fix the issue. Thanks ;)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Bill Sheboy
Unfortunately, this new rule just stopped working. Everything is exactly like before. In task and audit log rules are marked as success but fields in the task are empty.
I don't understand why it works at first and then it breaks down.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information, @Katarzyna Michalik
Just to confirm, are you saying the rule is not triggering when an issue is created, or that it is triggering and not updating the fields?
If it is the first one, would you please post the Rules details section? Those may indicate some limitations for who and when the rule triggers.
Also please note: this appears to be a project-level rule, only impacting rules for this project. If you wanted this to trigger for multiple projects, you would need a global or multiple-project rule instead.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This rule is intended to be used only in a particular project, so this is not an issue. However, I found something interesting. I tried two ways of adding a task.
1. In roadmap view and I used a plus next to the project to "create a child issue" - after creating the task, the automatic rule was marked as successful, but no field was updated.
2. I opened the project in a new window and used the plus sign to create a child issue - a new task was created and all required fields were filled in thanks to the automatic rule.
Is it possible to make sure that the automatic rules will be successfully working no matter how the tasks are created?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That is odd... I tried to reproduce your results and my rule fired in both cases:
One more thing to check: is the roadmap issue you tried to add a child issue to in the same project where the automation rule resides?
That is, for your project, does the board filter support multiple projects and so the roadmap includes issues from multiple projects? If so, I'd expect the rule not to fire when adding a child issue to a parent in another project.
If instead this is all one project, I believe you have discovered a defect. Please ask your site admin to submit a ticket to Atlassian Support here:
https://support.atlassian.com/contact/#/
Please post back here when you hear something back from them. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.