Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

[Gantt Chart Improvements] - View Window

Open
#3,924 1 comment 0 reactions 1 assignee View on GitHub

@Santiordon is already working on this.

Since Apr 2, 2026.

stale
Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

Description

Description

The user should be able to select from a dropdown to change the time window they are looking at. Currently, the time window is hard coded to show roughly 6 months of time. The drop down options should be the following:

  • "Week" which shows two weeks across the screen on a normal application window and highlights day numbers at the top
  • "Month" which shows two months across the screen on a normal application window and highlights week numbers at the top
  • "Half Year" which shows eight months across the screen on a normal application window and highlights week numbers at the top (slightly wider range than the current implementation)
  • "Year" which shows 18 months across the screen on a normal application window and highlights months at the top
    Across all views, each element should take up a proportional amount of time on the chart, although there should be a minimum screen width that each element takes up even if it is shorter than that on the timeline. While the dropdowns should be hard coded, the implementation should aim to abstract as much of the time window as possible such that adding different time frames in the future is a relatively easy task. the full functionality for viewing and editing should be available on every view.
Acceptance Criteria

The ability to select a view period via a drop down, rather than the current 6 month default view.

Proposed Solution

Update the Gantt Page with a new dropdown button, and potentially filter through results to only display what shows up. May also want to do backend filtering to help with speedups.

Mocks

N/A

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.