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 23
    • Issues 23
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-lrc
  • Issues
  • #344

Closed
Open
Opened Dec 11, 2015 by RingBot@RingBotOwner

LRC: Add more metadata to text recordings

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

With the increased use of text messaging (not with offline one), manipulating TextRecording object is now more and more common. Such new features need easy access to various metadata collected by the recording, but not currently easily exposed. The most pressing one is knowing if the recording contains relevant payloads. Some TextRecording may only contain "invisible" MIME payloads. In those case, raising the text widget and sending notifications is only spamming the user.

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