Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
E
ensalamento-back
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Ensalamento
  • ensalamento-back
  • Issues
  • #30

Closed
Open
Opened Feb 27, 2019 by bhmeyer@bhmeyerOwner
  • Report abuse
  • New issue
Report abuse New issue

Implementar subsistema de publicação do ensalamento

Atualmente, não há nenhuma especificação de qual é a instância correta de Ensalamento para um determinado semestre. A modelagem do sistema deve prever isso e rotas devem ser criadas para facilitar a visualização das salas das turmas.

Edited Feb 27, 2019 by bhmeyer
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: ensalamento/ensalamento-back#30