Skip to content

Forcing record creation after duplicate warning #2779

@knirirr

Description

@knirirr

The current way of doing this is:

  1. Fill in details for new record.
  2. Click submit button.
  3. Inspect list of potential duplicates to check that this isn't really a duplicate. If not, then...
  4. Click "I know what I'm doing".
  5. Click submit button again.

Step 4 confuses some users, who appear to think that clicking it should submit the record immediately. Perhaps we should do that, or offer a more obvious indication of the need to resubmit?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Awaiting feedbackAway user feedback regarding a specific implementation/feature
    No fields configured for Feature.

    Projects

    Status
    To do

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions