[Feature request] [UI] Roadmap enhancements and feature

Abierto
#464 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
go
Área
frontend

Línea de trabajo

The issue does not name files, tests, or an entry point. Start by reviewing the existing roadmap UI and the linked Gantt implementations, then clarify which proposed capabilities—length, dependency visualization, and completion percentage—are in scope. The work is ready to implement once those choices and acceptance criteria are agreed.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Hey there,
the current roadmap features is pretty neat yet has some problems and lack of features which can make it a big deal for any user(or at least me).
They key features are:

  • Length: Which needs an start date (it can be an optional field and/or with a task estimated length so we can just drag it and that records it as a feature of the length)
  • Dependability: Which is already implemented by link feature but it has to be visualized.
  • Percentage: The portion of the work that has been done (Work hours that has been logged can be used for this feature or as a separated metric)

Some other features are also available out there and there are good implementations which we can at least evaluate :

*Not affiliated by me
https://github.com/nelson820125/jordium-gantt-vue3
https://github.com/visuallyjs-svelte/gantt
https://github.com/ANovokmet/svelte-gantt
https://github.com/svar-widgets/gantt

I will be happy to know about your vision.

Lenguaje dominante
Go
Estrellas
421
Forks
50
Merge medio
17 h 34 min
PR fusionados (30 d)
80

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Windshiftapp/core

Todos los issues de Windshiftapp/core

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.