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
  • #310

Closed
Open
Created Aug 30, 2016 by RingBot@RingBotOwner

LRC - UserActionModel state is not properly updated for new outgoing call

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

When creating a new call in a client and selecting that call immediately, the UserActionModel (UAM) does not properly update the states of the actions. It seems this is because doing CallModel::getIndex() immediately after creating a new call results in an invalid index, thus the selectionModel can't be updated and the UAM relies on the selectionModel.
 

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