signify dependencies in the GANTT view and limit actions based on them
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
How to use GitHub
- Please use the 👍 reaction to show that you are affected by the same issue.
- Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
- Subscribe to receive notifications on status change and new comments.
Is your feature request related to a problem? Please describe.
Right now the GANTT view does not show the dependency relation between cards. Nor does it enforce the logical rules (if task 1 depends on task 2, then task 2 can't start before task 1).
Describe the solution you'd like
Add a line between the tasks to show the dependency
block changing the order when it would break the dependency order
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the GANTT view entry point and trace how cards, dependencies, and order-changing actions are represented. No file or test is named in the issue, so first locate the view and its action handling. Done means dependency lines are visible and actions that violate dependency order are blocked.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100