Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • gkwebapp gkwebapp
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 198
    • Issues 198
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gnukhata
  • gkwebappgkwebapp
  • Issues
  • #553
Closed
Open
Created Jul 31, 2017 by GNUKhata@gnukhatauserOwner

behaviour correction for last row in multiple accounts

Created by: Krishnakant

While creating multiple accounts, we must ignore the last row. This means that when user presses enter on account name field and if it happens to be the last row, we must check if the account name is empty and trigger save. here we asume that user was not wishing to create another row that's why enter was pressed without entering any thing. If there is name in the field then usual behaviour will follow.

Imported comments:

By Prajkta Patkar on 2017-04-07T12:23:52.567Z

mentioned in commit robaraskar/gkwebapp@d1063be7

By Prajkta Patkar on 2017-04-07T12:20:33.671Z

closed via merge request !500

By Abhi1tb on 2017-04-07T12:13:55.668Z

mentioned in merge request !500

Assignee
Assign to
Time tracking