Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-lrc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-lrc
  • Issues
  • #349

Closed
Open
Opened 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)

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-lrc#349