I have a scenario where I need to clear a particular field based on a condition and then populate the field with a specific value after checking if it's cleared. This worked when there are few issues to be updated but when the rule was triggered on a project where the issue count was more than 100 audit log showed performance issue.
I was wondering if it might be because of 2 actions in a single rule. Should I work on optimizing this? Please shed some light here?
Thank you!
I used to observe an issue with back to back creation of many tasks and sub-tasks. The automation would actually work but I would get a failure message. I spoke to Code Barrel (original vendor) and they acknowledged that there could be a false warning on such a scenario. Now, I have not seen this for a long while so I suspect it has been addressed. All that said, while it is possible, two action is not many at all. My rule had about 25 with several tasks being created and many sub-tasks. Still it is a reasonable theory that doing this on 100 issues could result in performance issues. Performance aside, is the rule succeeding? I wonder if you could somehow limit the number of issues being changed?
The rule is succeeding in a test project where I tested. This project has tens of issues to test the rule. In an actual project it did not succeed. The only difference is the count.
But it's good to know 2 actions is not much.
"Project = TJ AND Sprint in closedSprints() AND updatedDate > startOfMonth("-6")"
That was the JQL used. 6 months of data. Since the project is new the query only retrieves about 120 issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Multiple rules triggering on the Start of the Sprint for 3 different Actions should be ok too right? I am trying to split the rule with multiple actions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @sowjanya gondi , it's fine to have multiple actions on a single rule. You can have up to 65 components per rule.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you JD. I will keep that in mind. The problem might be because I was trying to clear a field and populate it with new value in the same rule. 2 actions in the same rule. That may have caused some conflict while performing on large number of issues.
I have now separated them out as 2 different rules.
Your advice is still helpful to remember for future work. Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.