Hold place

  • 4
  • Idea
  • Updated 3 years ago
  • Not Planned
I'm asking again for you to PLEASE PLEASE PLEASE fix the quirk that makes transactions scroll back to the top when a single transaction is opened for viewing or editing. This is incredibly frustrating!
Photo of E Coker

E Coker

  • 5 Posts
  • 1 Reply Like

Posted 3 years ago

  • 4
Photo of Colin Grant

Colin Grant

  • 376 Posts
  • 112 Reply Likes
That really is an irritating little bug - it is not a missing feature or an enhancement it is a flaw in the interface design. I love GB to bits it is a great app but the devs really should take time out and just go back and fix these little things, be they bugs or design flaws. Maybe they should start a list of the most asked for fixes and work to that - it could be a public list against which we all can vote. 
Photo of E Coker

E Coker

  • 5 Posts
  • 1 Reply Like
This bug is maddening! I have to click an extra time to load month-old transactions, and then scroll all the way back through them if I find a transaction that needs to be adjusted or viewed. Ugh!!
Photo of Colin Grant

Colin Grant

  • 376 Posts
  • 112 Reply Likes
I reconcile regularly so the need to go back more than a couple of days or so has not arisen. For that reason I don't have huge issue with this, but I agree it is wrong - if you edit a transaction then you want to stay with that transaction to ensure you edited it correctly.
Photo of Karisa Russell

Karisa Russell, Official Rep

  • 1751 Posts
  • 233 Reply Likes
Hi Colin and E Coker, 

Thanks for your adding your voices! I am sorry for the frustration with this bug, and I agree it's annoying.

Unfortunately, right now, we're not working on a fix for this as we're working on other things (check out our Roadmap for updates). I know that doesn't help you at this time, and I wish I could give you a good work-around. I'll be happy to let you know if we decide to move forward on this. 

Thanks
Photo of Colin Grant

Colin Grant

  • 376 Posts
  • 112 Reply Likes
That is a stock answer, Karisa and it is not helpful. How many bugs/idiosyncrasies in the interface are there that you are choosing not to work on because you are developing other functionality that might itself give rise to bugs that you will choose not work on right now! You know, paying users should not be left with the impression that you might not even bother to address an issue at all. It should not in general terms be a case of "if we decide to move forward" which seems to be your standard stance with a lot of the so called smaller issues. At least be upfront about this - if you have no intention of fixing something say so and say why.
GB is in lots of ways a very good product. I as do many others love its core functionality. It could however be a truly great product if these issues could be dealt with. Not all at once, but one or two with each update perhaps.
Photo of Karisa Russell

Karisa Russell, Official Rep

  • 1751 Posts
  • 233 Reply Likes
Hi Colin, 

I'm sorry you're not happy with my answer. To clarify, we do work on bug fixing regularly. In fact, we're working on a maintenance sprint right now (and have been for the past several months). During maintenance sprints, we almost exclusively work on bug fixing and other small updates. You can check out our Changelog for a more complete list of things we fixed recently. 

We are actively choosing to work on other things, and deprioritize this bug right now. I know that's not helpful for you, and I apologize. I can't say that we won't work on this in the future, but we are not working on this now. 

Hope that makes sense! 
Photo of Colin Grant

Colin Grant

  • 376 Posts
  • 112 Reply Likes
Thank you for that Karisa. Maybe the answer is to publish what you are doing re the maintenance sprints (maybe you do and I don't know where). That way any misconception that not a lot is being done will be alleviated. What do you use to determine what needs fixing first? 
GB, as I said, is a good product - I would like it to become great :-)
Photo of Karisa Russell

Karisa Russell, Official Rep

  • 1751 Posts
  • 233 Reply Likes
Hi Colin, 

We appreciate the potential you see in GB! We're right there with you in wanting GB to be great. 

We do publish our plans for features or enhancements on our Roadmap. We don't publish what smaller fixes are being worked on in maintenance sprints. But, in those sprints, our priority are bugs that affect the most amount of people, or a bugs that are very severe. Because we are small, we decide to fix bugs / build features that have the most impact for the most amount of budgeters. 

I know it seems like we aren't working on the stuff that you care about. But, to be fair, GetSat is only one channel that you see feature requests or bug feedback on. But, there are other channels that you cannot see where folks are requesting features and posting bug feedback. We have to consider all channels, not just the threads on GetSat. 

Hope all of this makes sense.
Photo of Debbie

Debbie

  • 2 Posts
  • 1 Reply Like
I agree that this "quirk" is frustrating as sometimes I cannot find the update I made to the single transaction. I'd like to see the transaction in the group on the home page after an edit, even if I've changed the date, after I close the single transaction. That's where I get a bit frustrated as it takes time to scroll down to find the changed transaction. However, since so many people have commented about it I'm sure down the road we'll see a fix.
Photo of J

J

  • 11 Posts
  • 0 Reply Likes
The fix for this would be for the developers to:

* Save scroll position and restore it when coming back to the app
* Optionally notify the user with a bar on the top of the screen if there is a new transaction or transactions (pressing the bar would scroll up)

See https://stackoverflow.com/a/18844780 for example code for doing this.

Karisa, can you please pass this along to the developers and product offering managers for possible inclusion on the roadmap?  Hopefully when they see the example they will think it's a bit easier and faster to implement than perhaps they imagined.
Photo of J

J

  • 11 Posts
  • 0 Reply Likes
For your product team: I also wanted to note the use case where the current design poses a problem.  When I am reconciling transactions, I have to switch out to another app (my banking app, or my banking notifications).  Isn't reconciliation a common use case?

Every time I flip back to Goodbudget, Goodbudget scrolls back to the top of the list, presumably to say "yay! I refreshed your list with the server's copy of the list again!" and I have to go hunt down the spot I was in.  Repeat over and over again for every single transaction I'm trying to reconcile.
Photo of John Vander Stel

John Vander Stel

  • 287 Posts
  • 86 Reply Likes
Karisa,

I've suggested this before and I will suggest it yet again right here for added emphasis! 

Transparency on the efforts of the GoodBudget team is continuing to be a major problem for users and the GoodBudget team, as well.

I again suggest putting a link on GetSat (your user's official suggestion and complaint forum) that shows what the GoodBudget is currently working on.  Putting that link only on the official app web page is not putting it where your users are asking the questions and offering suggestions! 

That would make the team's development efforts more transparent and would then not leave GoodBudget users out in the dark on the team's efforts all the time.

This transparency problem keeps getting brought up over and over again, causing hard feelings among GoodBudget users... never being fixed proactively.

I also suggest offering a link in the same place that actually shows the priorities that have been established by the team for future work.  That transparency would then also offer much-needed user input that could provide suggestions on changes to established priorities, as well.  This resource (in the right place) would be helpful for both GoodBudget users and the GoodBudget team, as well... thus offering transparent prioritization, as well. :-)

This could finally put an end to the endless questions and complaints about why certain suggestions and bugs are not being worked on and the continuous canned responses by the team.  :-)

It could offer the users a rough idea about when and if their suggestions and complaints will actually be addressed, and also if they are, in fact, already being addressed! :-)

Again, this is just my 2 cents, for what it is worth...

John Vander Stel
Grand Rapids, Michigan
Photo of Colin Grant

Colin Grant

  • 376 Posts
  • 112 Reply Likes
I just gave up, John, I will not be renewing my subscription and am already using alternative software. The approach adopted to bugs is astounding, pathetic and altogether unacceptable. I am  not paying for that sorry!
Photo of J

J

  • 11 Posts
  • 0 Reply Likes
So I am curious what this alternative software is?

Every budgeting app I've tried has had multiple things I thought could be improved. This isn't the worst problem in the world. While we wait for the Goodbudget team / Dayspring to re-evaluate the priority of this request, there are at least two workarounds:

- Use airplane mode to prevent Goodbudget from syncing
- Use two devices to reconcile, with Goodbudget constantly open on one device and your account on the other.
(Edited)
Photo of Colin Grant

Colin Grant

  • 376 Posts
  • 112 Reply Likes
What I now use is irrelevant. Anything is better than listening to the same old same old the support spew out on these forums as far as bugs are concerned. They do not prioritise bugs that come from their own coding, not unless those bugs are really bad. Anything else is left for the user to workaround - because this is not n their radar at present! My accounts have all now been deleted as has my automatic renewal.