Hi. I’ve got a really weird glitch where the VWRL time-weighted rate of return comparison doesn’t appear to have updated since 1st February. I can see my portfolio performance up to date, but the tracking of VRWL hasn’t updated since the start of the month. Is anyone else experiencing this? I’ve tried clearing cache etc
2 Likes
So it does, it shows as ended on 1st February for me too.
1 Like
same here
@acamp could someone take a look at this please as the VWRL comparison data still isn’t updating past 1st February? Thanks
1 Like
whoops I thought I responded here - flagged to the team yesterday who are working on it!
2 Likes
Hi! Any news on this? It’s been a long time; what’s the reason for this bug to be so persistent?
Nearly two weeks since I reported it and still not resolved. Surely this can’t be that difficult to sort out?!
5 Likes
Hi @acamp is there any news on this? The month is almost gone and the glitch is still present (at least for me) with no reference data Feb 1st onwards.
1 Like
Definitely not just you!
1 Like
Doesn’t leave me with the greatest sense of confidence that something like this isn’t resolved after nearly a month, what if it was something more significant.
5 Likes
Same, approaching a month and they still can’t fix this… what’s going on, it’s not like your dev team is packed releasing new and innovative features !
2 Likes
Not defending the delay in this being resolved
But understanding how it would be worked through in a Dev team, they’ll likely follow a normal bug categorisation e.g. priority and severity being the main two
This wouldn’t get categorised that high unfortunately, as much as people may think or want.
Normally a bug would get a priority and severity, with a number between 1 and 4 (and sometimes 5 for priority) with 1 being highest
I’d guess this falls under a severity 3/medium it doesn’t impact the main functionality of the app (buying, selling etc), so gets fixed in an appropriate future release and doesn’t get rushed through or hotfixed.
1 Like
Given the visibility of this bug. I would have classified it as high priority. It doesn’t make freetrade look very professional or a reliable place to store money. As a hot fix they could at least put a message on the screen to say it’s being fixed.
3 Likes
There in is how the debate goes within a Dev team, a consensus is reached and the bug gets categorised, to me it’s a more visual error (and/or data retrieval error) which is inconsequential to the main functionality of the app.
There are obviously a lot of other factors and more nuance to this, than can come across in a forum post, it also helps having worked in or worked with a Dev team to understand these processes
I agree it doesn’t look good and the comms in this case could be better.
2 Likes
As a senior software developer for the past decade I have an in-depth understanding of the life cycle of a project and the priorities of a dev team.
This is a public facing feature which is broken and has been broken for a month, Freetrade charge customers money… this isn’t a charity app made by two dude’s in a garage, it s a commercial project intended to make money… even worse, it holds millions in customers cash and they can’t even get a comparison graph working.
And don’t get me wrong, am absolutely not coming at you woody. But as an investor in Freetrade, I have cash on the line and to see this is infuriating.
10 Likes
Have to agree to disagree on the significance of the feature (in comparison to other app features) and whether it warrants a hotfix or quicker resolution in this scenario as it’s played out so far.
I do get both sides as one of those paying customers as well
I don’t feel a need to disclose my specific involvement/experience level within the IT sector, but I can say I’m well informed of the SDLC.
I’ll leave my input at that…
1 Like
@acamp can we please have comms on this?
2 Likes
@adam @Viktor @Ian @acamp @Freetrade_Team
It’s pretty embarrassing that such a visible bug has been there for more than a month. I’m sure there must be some reasonable explanation about it. But what’s really beyond me is the radio silence about what’s going on despite many prompts here.
I contacted support about this too several weeks ago, all I got was “reinstall your app” which obviously didn’t help. No further discussion. They weren’t even aware that this is a widespread problem.
I’m not even going to get started on the other graph bug I have which has been unresolved for 1.5 years now.
This is really terribly disappointing.
5 Likes
They are very busy in developing advanced features!
Hey @mig
Apologies for the radio silence on this. We’ve raised a ticket as this is a known bug and I’ve chased the team to see what the hold up is. The reason is that our data provider has been sending empty data and has been unresponsive since about how we resolve this.
We’ll get this sorted.
Best,
Alex
3 Likes