Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.web beat.web
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.webbeat.web
  • Issues
  • #245
Closed
Open
Issue created Aug 04, 2015 by André Anjos@andre.anjos💬Owner

[reports] Sharing/locking behaviour

How can one show a report to somebody else not sitting immediately by his side? Despite the fact other objects are shareable at the platform, reports and attestations need to be locked before they can be shared. I wonder what would be the workflow to collaboratively create a report or (on a minor scale) an attestation.

Differently than attestations, reports combine displaying features that authors (working remotely) may need to agree while composing an article. IMO, being able to share a report sounds like a good idea.

Attestations don't suffer from this problem because, if you lock them, other people can see it. Reports, on the other end, can only be seen while locked so the user would have to:

  1. Lock report
  2. Share link with remote party
  3. If comments from remote party: unlock report (now not visible anymore to remote party)
  4. Modify the report and go back to 1 as many times as necessary

This looks a bit cumbersome - would you agree? In this context, would it make sense to have reports a subclass of "Shareable" as suggested on one of our discussions?

Assignee
Assign to
Time tracking