请求修复Github Milestone Cumulative Flow应用的两类核心问题

I’ve put together targeted code fixes for the first two issues you’re facing with the Milestone Cumulative Flow app. Here’s how to address each one:

Issue 1: Points only counted when at least one story is "in progress" (has actual start date) #

The root cause here is that the app’s filtering logic only includes stories with an actualStartDate (tied to the "in progress" state). To fix this, we need to adjust the story filtering to include all stories linked to the target milestone, regardless of their actual start date.

Code Adjustment: #

Find the section in the code where stories are filtered for inclusion (likely in a data processing or aggregation function). Look for something like this:

// Original code
const eligibleStories = allStories.filter(story => story.actualStartDate !== null);

Replace it with this logic that focuses on milestone association instead:

// Modified code: Include all stories linked to the target milestone
const eligibleStories = allStories.filter(story => story.milestoneId === currentMilestoneId);

Why this works: #

This removes the dependency on actualStartDate, so all stories tied to the milestone (regardless of their current state) will have their points counted. You won’t need to create dummy "in progress" stories anymore.

Issue 2: Points not counted for cross-project stories in Epics (when the story's project has no milestone-linked Epics) #

The app is currently checking if the story’s parent project has any Epics linked to the milestone, which excludes stories from other projects even if they belong to a milestone-linked Epic. We need to bypass this project-level check and validate directly against the story’s Epic association.

Code Adjustment: #

Locate the part of the code where project-level filters are applied to stories. You might see code like this:

// Original code
const projectHasMilestoneEpic = story.project.epics.some(epic => epic.milestoneId === currentMilestoneId);
if (!projectHasMilestoneEpic) {
  return; // Skip stories from projects without milestone Epics
}

Replace it with logic that checks if the story’s own Epic is linked to the milestone:

// Modified code: Check if the story's Epic is part of the milestone
const milestoneEpicIds = currentMilestone.epics.map(epic => epic.id);
if (!story.epicId || !milestoneEpicIds.includes(story.epicId)) {
  return; // Only skip stories not linked to a milestone Epic
}

Why this works: #

This shifts the check from the project level to the individual story’s Epic association. Stories from other projects that belong to an Epic tied to the milestone will now be included in point calculations, eliminating the need for dummy Epics in other projects.

Note: Depending on the exact structure of the app’s code, variable names or function locations might vary, but these core logic changes should resolve the two issues.

内容的提问来源于stack exchange，提问作者N.G.