OSDG-IIITH / OSDG-IIITH/formsiiit

Issue Tracker

Open
#2 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Svelte
Stars
7
Forks
5
PR merge metrics
No merged PRs in 30d

Description

Known Issues
  • Current profile & logout option not shown anywhere
  • Fix UX

Form Editor

  • Initial Title and Description are not proper placeholders.
  • FIX DOUBLE CLICKS
  • Comments & Settings buttons are messed up (especially on mobile)
  • Clicking on the placeholder input for a 'Text' question unchecks the 'Required' checkbox. (Fixed by #5)

Responses

  • Responses page unfinished
  • Faulty Alignment in Statistics card
  • Last response shows negative values when form is newly created and responses are given immediately
  • Responses Graph doesn't exactly work (missing endpoints)

Permissions

  • Alignment issues in Data Table

Mobile

  • More space on edges (limit width)
  • Comments & Settings Panels
  • No menus

General

  • Error Reporting

Backend

  • Anonymous Responses
Missing Features

Homepage

  • Missing Tabs (Filled Forms, Shared Forms)
  • Add link to create/edit groups page
  • Use backend pagination
  • Add templates

Form Editor

  • Image Section
  • Question Add/Remove Animations

Backend

  • File uploads

Groups

  • Allow groups to be used to grant/revoke permissions

Responses

  • Finish Responses Page
  • Delete response button
  • Question-wise Analysis
  • Export to CSV
Additional Features

Refactor

  • Separate out chips code and use it in other questions types
  • Migrate types to $lib/types.ts

Form Editor

  • More 'options' for Input/Textarea
  • Once a form is created, provide a link to share it (prominently to the user - a copy to clipboard feature)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

This is a broad checklist covering the homepage, form editor, responses, permissions, mobile UI, backend, groups, and refactoring. Start by selecting one unchecked item and locating the corresponding project area; the issue names no files or tests. Done means that one selected problem or feature is implemented and verified without taking on the remaining checklist.

Written by the indexing model from the issue text.

Assessment

Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.