Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
concrexit
concrexit
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 70
    • Issues 70
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 10
    • Merge Requests 10
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • thalia
  • concrexitconcrexit
  • Issues
  • #814

Closed
Open
Opened Jan 28, 2019 by Sébastiaan Versteeg@sversteegOwner

Better implementation events informations fields

One-sentence description

Better implementation events informations fields

Motivation

The fields are currently (mis?)used in ways that we have not foreseen. It seems that committees have found different use cases for the fields Frankensteining them in ways they were not meant to be used.

For example: list selection, using plain HTML to describe a field. Something that doesn't work in the app because it renders the description as placeholder.

Screenshot_2019-01-28_at_12.04.00

Desired functionality

I'm not sure how we should change this functionality, probably a way to create dropdown selectboxes for the kind of questions in the example. That's why we should look into this, maybe with the people that use them the most (educacie?)

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: thalia/concrexit#814