Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
  • Sign in / Register
jami-project
jami-project
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
    • Insights
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
    • Locked Files
  • Issues 172
    • Issues 172
    • List
    • Boards
    • Labels
    • Milestones
  • Security & Compliance
    • Security & Compliance
    • Dependency List
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-projectjami-project
  • Issues
  • #273

Closed
Open
Opened Mar 17, 2016 by RingBot@RingBot
  • Report abuse
  • New issue
Report abuse New issue

new call state: participant

Issue generated from Tuleap's migration script. Originally submitted by: Nicolas Jager (nicolasjager-sfl)

hi,

the summoner of a conference knows that the call is a conference trough :

Call::Type::CONFERENCE

but for the participants, the conference is like usual call :

Call::Type::CURRENT

wich leads to have two previews on participants screens. I propose to add a new state and let the conference summoner to tell to the participants that they are currently involved in a conference with it.

In that case we could shutdown the preview.

bug7a

Related issues

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
1
Labels
invalid
Assign labels
  • View project labels
Reference: savoirfairelinux/ring-project#273