Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
hotpotato
hotpotato
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 5
    • Merge Requests 5
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Hot-Potato
  • hotpotatohotpotato
  • Issues
  • #111

Closed
Open
Opened Aug 08, 2019 by Zac Pullar-Strecker@zacpsMaintainer0 of 1 task completed0/1 task

Escalations: Require permission from a team to receive escalations

The following discussion from !128 (merged) should be addressed:

  • @zacps started a discussion: (+2 comments)

    I didn't change the permission for setting a team to escalate to another team.

    Ideally this seems like it should require permissions from both teams, but I'm not sure if there's a good way to do this with the current permissions scheme. Requiring the permission from the context of the Hot Potato team might be a good alternative?

    Either way I'm not sure whether this needs to be included in this pull or not.

  • @rhysmd

    I think the idea was to have a prompt of some kind come up for the other team, allowing them to accept or reject so two people with separate permissions in each team?

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: Hot-Potato/hotpotato#111