Feature #92618


Epic #98292: [UX] - Keep a fresh look and feel

Introduce "next" button in the doc header

Added by Alex Nostadt over 3 years ago. Updated 17 days ago.

Should have
Backend User Interface
Target version:
Start date:
Due date:
% Done:


Estimated time:
PHP Version:
tca, buttons, mass update, UX
Sprint Focus:


While creating a complete new record the current buttons (save + close, save etc.) are enough I would find it handy to have a "next" button which automatically opens the next record for editing though. This would allow editors to quickly update existing records once new fields have been introduced which may even be required. Yes, there's the mass edit feature accessible from the list view but this does open all records with selected fields at once which can become slow. In addition valuable context probably miss - other record fields.

Some things to consider are:

- what if someone edits the next record already?
- what if the next record is deleted? (suggestion: skip to the next editable)
- what if the next record has editlock activated? (suggestion: skip to the next editable)
- what if there's no next record? (suggestion: gray out and disable the button)

What do you think about that?

I hope that's the correct category. I am unsure about FormEngine vs Form Framework

Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Epic #93528: Backlog of UX ideas for EditorsNew2010-11-11

Actions #1

Updated by Benni Mack over 3 years ago

  • Target version changed from 11.0 to Candidate for Major Version
Actions #2

Updated by Riccardo De Contardi over 3 years ago

  • Related to Epic #93528: Backlog of UX ideas for Editors added
Actions #3

Updated by Annett Jähnichen almost 2 years ago

  • Category changed from FormEngine aka TCEforms to Backend User Interface
  • Parent task set to #98292
  • Tags changed from tca, buttons, mass update to tca, buttons, mass update, UX
Actions #4

Updated by Riccardo De Contardi 17 days ago

  • Status changed from New to Closed
  • Target version deleted (Candidate for Major Version)

There has been no activity on this topic since a lot of time; moreover we would want to keep the interface as slim as possible and this feature seems fit for an extension rather that being in the core.

for these reasons I close this issue for now;

if you think that this is the wrong decision or there is still work to do here please reopen it or open a new issue with a reference to this one.

Thank you and sorry for the late feedback.


Also available in: Atom PDF