Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • jami-project jami-project
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 165
    • Issues 165
    • 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-projectjami-project
  • Issues
  • #183
Closed (moved) (moved)
Open
Created Dec 02, 2015 by RingBot@RingBotOwner

Share context menus between clients

Issue generated from Tuleap's migration script. Originally submitted by: Emmanuel Lepage Vallee (elv13)

This issue track the advancment of the shared context menu implementation designed and discussed in May. The implementation was done in spare time by Stepan and me since May.

* Create the UserActionModel (done, May)
* Define a set of actions for each assets (done, May)
* Allow to define context for assets (done, June)
* Abstract access to assets across all models (done, August)
* Port the UserActionModel to the unified asset access (done, October)
* Move action code from clients into LRC (WIP)
* Add a platform specific extension interface (Unstarted)
* Support tree based actions (Unstarted)
* Support multi selection actions like join calls (WIP, postponed)
* Integration into all clients (Unstarted)

Assignee
Assign to
Time tracking