Hi all!
Super weird issue popped up this morning.
We are on data center 9.4.15 and using Automation for Jira for a number of rules, particularly assigning rules on issue creation. These rules have been working great for months. We haven't updated workflows, the plugin, or Jira for weeks. At about 9:45 this morning, Automation for Jira stopped recognizing the issue created trigger on all rules that use it. We've had dozens of issues created this morning, but all the audit logs on those rules are blank after 9:45, meaning they aren't being recognized as triggers.
The ONLY changes we have made is we are in the process of archiving a large number (like 33,000) issues from one particular project. I have been doing these in the bulk editor 1,000 at a time since yesterday afternoon, but haven't reindex the whole site yet. I am in the process of reindexing that particular project, but rules on other projects have been affected as well.
Any ideas??????
Thanks in advance!
Finished reindexing the project we're running the archive on and everything is working again. Maybe it was just using too much memory?? Weirdest Jira thing I've ever seen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nothing since 9:45am, although the new issues we've created are triggering other rules when fields are changed. I have 1 rule that shows some config changes just because I was messing with it when I was troubleshooting. I was able to get that one to run manually and they ran fine yesterday and early this morning, so it's not the configuration.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Do the rules run if you run it manually? You might want to look at the workflows to make sure the create issue event is firing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
They do and I have. All the workflows haven't been touched since December and they all fire an issue created event.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Does a single rule run on the issue created event? Could another rule be getting in the way? If so could you see if this is checked on your rule “allow other rule actions to trigger this rule”.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nope, as far as I can tell, none of them are working. And I always set my rules up to allow others to trigger them.
The weirdest part is that they worked fine for MONTHS until a couple hours ago and none of our configurations have changed, unless it is related to the archiving project.
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.