Closed abbyad closed 6 years ago
I agree with @bishwas-medic - this module needs a complete rewrite either using postgres (via couch2pg) or using targets (2.x only). I don't think we have time to do this in this iteration.
I think this should be bumped to the next iteration as we are more than halfway through the current iteration. Let's hold off for now and consider options for either fixing this bug or increasing the priority of the re-write.
Thinking about this a bit more, let's see if there is something simple we can do to fix this. If not, we would have to hold off until a later release.
Just want to highlight that there are potentially two issues here, and that they are related only in that they both rely on getting subsets of forms with Nepali form codes: 1) Form filters in the Reports tab are not returning the correct forms 2) Analytics widget showing incorrect values
I think it makes sense to deal with Analytics during a rewrite, but the form filters not working is a more immediate concern. Also, there is a chance that solving it may also lead to a quick fix to Analytics without it needing a rewrite.
This could be an internationalisation issue if filtering forms by unicode characters isn't working as expected...
Ok, I've done some investigation and can't see a quick fix.
I can't reproduce the reports filter bug and it looks to be caused by changes not being filtered so as changes come in they gradually pollute your filtering. I vaguely recall us fixing a bug for that but can't find it now... As this instance is top priority for migration to 2.x I propose getting the upgrade out and trying to reproduce the error with recent code. Perhaps we should add this to the migration testing for this instance?
I did see the ANC Analytics issue. That may also be fixed by upgrading to 2.x but I'm not confident that the in-app analytics are production ready regardless of this specific bug. Can we get them using klipfolio instead, perhaps via couch2pg? It's not in-app but it's the next best thing. We have some ideas about replacing in-app online-only analytics with either embedded single sign-on klipfolio or direct queries against postgres.
@abbyad Thoughts?
Thanks Gareth, let's revisit the filtering and analytics post upgrade to v2.
Closing until it happens in 2.x
Added AT to this issue so that we do come back to it on v2.
Are we able to AT this at this stage @abbyad @sglangevin ?
This should be tested on the cloned/upgraded version of the instance where it was originally reported, if possible. We should coordinate with @bishwas-medic
Did a quick check with the ANC widgets in a clone instance running v2.11.0-alpha. I can confirm that the issues still persists. Here are few issues that I could verify:
Reopening the issue as it is happening on v2.x too.
@bishwas-medic please test the filtering issue as well and feedback on whether or not that is working. Which project were you testing on the cloned instance?
All the filters for Reports seems to be working fine. I will DM you the name of the instance since this thread is public.
Closing as the original issue is resolved:
We are not supporting this ANC dashboard in v2, so I'm closing this issue as the report filter piece is resolved.
We are seeing an issue in a project where filters and analytics are not working properly on a v0.4 instance.
We have not yet had other reports of this issue. The project in question is using Nepali characters for form codes - which may be responsible of the issue or a red herring.