Skip to content

[Feature] Clarification on Sprint Support and Project Planning Direction #10896

@AlexMattyou

Description

@AlexMattyou

Hi Huly team,

While exploring the codebase, I noticed that Sprints were renamed to Milestones in PR #3192.

I'm trying to understand the long-term direction of Huly regarding project planning.

Many teams use Sprints for:

  • Backlog → Sprint planning
  • Sprint goals
  • Sprint start/end dates
  • Team capacity planning
  • Story point estimation
  • Sprint reports
  • Burndown charts
  • Velocity tracking
  • Moving unfinished work to the next Sprint

My question is:

  • Are Milestones intended to become the replacement for Sprints and eventually support these workflows?
  • Or is Huly's philosophy to keep planning simpler and avoid Scrum-style Sprint features?

I'm also interested in contributing to Huly.

If Sprint-related functionality is something the project would welcome, would a well-designed PR be considered? Or does it go against the current product direction?

Thank you for any clarification.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions