Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-libclient
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 15
    • Issues 15
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-libclient
  • Issues
  • #309

Closed
Open
Created Sep 06, 2016 by RingBot@RingBotOwner

LRC: calls which are ongoing in the daemon when a client is launched don't show up in the RecentModel

Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)

If a call is ongoing in the daemon at the time a client is lauched, LRC seems to be aware of the call in the CallModel, but it doesn't show up in the RecentModel.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking