Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
briar
briar
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 693
    • Issues 693
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 16
    • Merge Requests 16
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • briar
  • briarbriar
  • Issues
  • #960

Closed
Open
Opened May 31, 2017 by Ernir Erlingsson@ernirDeveloper

Contact Introduction confusions and redundancies

Background

This ticket lists all the issues observed during contact introduction during user testing and a robust internal test. Some of these might be "features" or already listed as issues in other tickets.

Results

1 Some testers were confused why nothing happened after accepting the introduction, confirming #923 (closed) .

2 It's possible for the same user to introduce the same two contacts as in a previous introduction even when the two contact's have not yet responded to the initial introduction. Multiple simultaneous introductions, with the same pair of contacts, were confusing for the introduction recipients.

3 If A has declined the introduction that information is not displayed for B until he/she has selected decline/accept introduction. I wonder if it would not be simplest just to display the rejection immediately before B answers ?

4 If two contact's are introduced to one-another that are already contacts, unbeknown to the introducer, there is no need to propagate rejections between the two contacts.

Ex. User's A and B are already connected. User C introduces A and B to one another, A decides to reject. B receives introduction from C but also the rejection from A, which caused confusion. In this case it would have been best to skip displaying the rejection entirely because it is completely irrelevant.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: briar/briar#960