Why when clicking on save and new the cursor doesnt return to the supplier box?

Hi sjr_accounts Thanks for reaching out to us here on the Community. The cursor returning to the payee box was a feature that existed some time ago however after an update, approximately 12 months ago, it shouldn't been available. Some of our customers have reported that the option did remain however if that option is no longer available for you then we're not able to re-instate it. You could try clearing the cache and cookies for all time on your browser or use an incognito/private window to establish if the function re-appears.

Sorry @John C  but we've done all this before - several times.

Having the cursor return to the first input box on a new entry is not a feature - or something that would be nice to have - it's basic programming for any date entry system.  It's AN ABSOLUTE MUST.

The cause should be well known to your developers - they've broke it & fixed it several times in the last 18 months or so.

It isn't due to cookies, caches or anything on our end.  It's due to poor coding & woeful quality control.

Please @John C - rather than fob users off with things like it's an update - you'll like it in the end, elevate this to the developers.  Faults like this make QBO an absolute PITA to use.

@FWS Rhonda , @CarolB , @LMontville , @noboots , @Mower2 , @finance-fairoaks , @193514518254369 , @Shannnon714 , @DavidHarington , @FEDUP247 , @Mark Armistead , @Jwestwood 

for any date entry system  for any data entry system

Hi, I spoke to someone on the online chat a couple of weeks ago, I sent him a link to this thread, he had a word with the engineers and they told him that it has never been possible for the cursor to go to the name field automatically after clicking save & new! The help guy was as bewildered as me and suggested I take a video if it ever gets fixed.... UNBELIEVABLE!!

Just waiting on the next thing they'll break, probably the internet knowing this lot and call it a feature.

I know I keep calling for a chnage log, it's should be a bug reinstatement log at this rate.

I'm staggered by your reply @John C. Just unbelievable.

@John C - any update on this?

Please confirm you have submitted as a bug (trust me, whatever you're primed to say, it is!).

It is a massive time-waster.  As I've posted multiple times when this bug has appeared in the past, it slows you down & makes QBO a real PITA to use for anything more than a few transactions at a time.

P.S.  I notice that you've recently been suggesting that users post their own reports/requests to https://feedback.qbo.intuit.com - please take a look at this site yourself (particularly the AppTransactions page), it's FULL of spam posts so the chances of the developers taking anything posted on here seriously are ZERO.

Any bug report MUST come via you & your colleagues on this forum (we all know that the Cog Wheel Feedback button is not worth the energy it takes to click).

Hi paul72, thanks for your post

This is not currently being treated as a product issue and would need to be included in a future update as an enhancement request. 

We appreciate this may not be the news that you want to hear, however, this is the information that we have to share at this time. 

To share feedback with our UK Product team, please see the in-product feedback tool or visit our Idea Exchange forum. 

Thanks again for reaching Intuit support. We'll be here if you have any further queries. 

I appreciate the reply @GeorgiaC but we're not asking for an ENHANCEMENT - we're asking for a clear & obvious bug to be rectified.

We discussed this at length last year & early this year too I think.  This is a bug that has been caused by bad coding (as above, the coders will know where because it's happened several times before).  This is a bug that's been allowed to go into production due to an abject lack of quality control.

There is a perfectly apt post in the Idea Exchange Forum - Sometimes you just need to leave it alone!!

It was quickly closed!

Tells you everything, I think.

Hi paul72 Thanks for your comments/feedback, I've submitted them to our developers.

It's like groundhog day in here at time with the replies from Intuit reps.

Thanks @John C 

Do you have the issue report / ticket number?

I would like to get a progress update on the fix to this coding bug.

Hi Paul, we don't have issue report/ticket numbers for feedback shared internally

As mentioned previously, this is not currently being treated as a product issue meaning there is no progress update to share. Please press the tab key or use your mouse to activate the field on the form. Thank you. 

I know that's the company line @GeorgiaC  but how many more times do we - as users - need to say it?

This IS a product issue.  That's why we're all so b'''''y frustrated.  This is due to bad coding.  It's a bug; a cockup; a failure of quality control.  Call it what you will but it needs fixing.

It is basic.  In every other data entry system I have used, a new form screen is ready to accept text.  You shouldn't have to select the natural first box to type.

Are you seriously suggesting that Intuit/QBO is right & everyone else is wrong?

The developers have changed something in the coding base that's taking the cursor away from the input box.  I haven't done any coding in donkeys years - but I think it used to be called Focus attribute.

The same issue means you have click twice on the product/service dropdown on an invoice/bill form before it will allow you to type.

If it's because the code has been optimised for touchscreen (rather than PC) then let them say this.  Every other data entry system copes with the differences between touch & keyboard entry.  It's been fixed before (without world-ending implications), so it can be fixed again.

Rather than fob users off with things like it's an update - you'll like it in the end, please elevate this to the developers AS A FAULT/BUG (not as feedback or a suggestion please).

Faults like this make QBO an absolute PITA to use.

@FWS Rhonda , @CarolB , @LMontville , @noboots , @Mower2 , @finance-fairoaks , @193514518254369 , @Shannnon714 , @DavidHarington , @FEDUP247 , @Mark Armistead , @Jwestwood 

Hi paul72, thanks for your response

We've escalated this to our Product team previously, and the advice is that the behaviour is working as expected. For this to be changed, it would need to be included in a future update of the product. 

We're again sorry that this isn't the information that you'd like to hear, and we appreciate your patience in this matter.

... but it isn't working as USERS expect @GeorgiaC  

Therefore, by definition, the UI/UX is faulty!

Even the assertion that it's working as the product team might expect is demonstrably wrong.

EXAMPLE ... If I go for a NEW Invoice / Bill / Expense, etc.  The cursor is where I'd expect it to be - in the Name Field ready to accept text input.  However, if I fill in the form & click Save & New (or keyboard shortcut ctrl-alt-s), I get exactly the same Invoice / Bill / Expense form but have to click the Name Field before it will accept text.

How is that working as expected?

It's the same input screen but two different experiences.

wow @GeorgiaC did the devs actually tell you this will need updating as a feature, a cursor in a data field is NOT a feature. As @paul72 has said it's a standard on ALL data imput forms.

Beggars believe.