Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[BUG]: respect granularity when limiting analytics time-series buckets

Open Beginner friendly
  • Is something wrong?
#333 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@Sparsh2105 is already working on this.

Since Oct 11, 2026.

  • #334 by @Sparsh2105 — open

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
analytics

Research direction

Read src/services/analytics.js and the existing tests in src/services/analytics.buildTimeSeries.test.js. Check how buildTimeSeries handles weekly and monthly buckets and how the tests verify bucket counts and ordering. Done when monthly results are capped at 12, weekly results at 26, and the results remain chronologically sorted.

Written by the indexing model from the issue text.

Description

bug
Bug Description

The buildTimeSeries function in src/services/analytics.js limits its output to the last 12 buckets regardless of the selected granularity.

As a result, the Weekly view displays only approximately 12 weeks of activity (~3 months), while the Monthly view can display up to 12 months of activity. This creates inconsistent historical windows when switching between granularities.

The function already accepts a granularity parameter, but the final .slice(-12) applies the same limit to both monthly and weekly buckets.

Expected Behavior:

  • Monthly granularity should retain up to 12 buckets (~12 months).
  • Weekly granularity should retain up to 26 buckets (~6 months).

Actual Behavior:

Both granularities are limited to 12 buckets, causing older activity to disappear from the Weekly view.

Proposed Fix

Use a bucket limit based on the selected granularity instead of hardcoding the limit to 12:

const SLICE_COUNT = granularity === 'weekly' ? 26 : 12;

return Object.values(buckets)
  .sort((a, b) => a.date.localeCompare(b.date))
  .slice(-SLICE_COUNT);

This allows the Weekly view to retain up to 26 buckets while preserving the existing 12-bucket limit for the Monthly view.

Testing

Update src/services/analytics.buildTimeSeries.test.js to verify that:

  • Monthly granularity returns at most 12 buckets.
  • Weekly granularity returns at most 26 buckets.
  • Weekly granularity can return more than 12 buckets when sufficient data is available.
  • Results remain sorted chronologically.
Scope
  • Implementation: src/services/analytics.js
  • Tests: src/services/analytics.buildTimeSeries.test.js
  • No UI, layout, or API changes are required.
Steps to Reproduce
  1. Run the application locally using npm run dev.
  2. Explore an organisation with sufficient issue or pull request history, such as AOSSIE-Org.
  3. Navigate to the Analytics page.
  4. Click Run Complete Analysis to populate the time-series chart.
  5. Select Monthly granularity and observe the displayed date range.
  6. Switch to Weekly granularity.
  7. Observe that the chart displays at most 12 weekly buckets, even when older activity is available.

The issue can also be reproduced by passing more than 12 distinct weekly buckets to buildTimeSeries in src/services/analytics.js.

Logs and Screenshots

No error logs are expected because this is a data truncation issue rather than a runtime error.

A screenshot comparing the Monthly and Weekly analytics views would help demonstrate the inconsistent historical windows.

Relevant implementation: src/services/analytics.js, where the returned buckets are limited using .slice(-12).

Relevant tests: src/services/analytics.buildTimeSeries.test.js.

Environment Details
  • OS: Ubuntu 26 LTS
  • Browser: Brave (Chromium-based)
  • Runtime: Node.js 22.22.1
  • Project: AOSSIE-Org/OrgExplorer
  • Setup: Local development environment using npm run dev
  • Additional context: The issue concerns the time-series bucket limit in src/services/analytics.js.
Impact

Medium - Feature works but has issues

Code of Conduct
  • I have joined the Discord server and will post updates there
  • I have searched existing issues to avoid duplicates
Dominant language
JavaScript
Stars
42
Forks
124
Avg merge
2d 22h
Merged PRs (30d)
10

Getting set up

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.

More from AOSSIE-Org/OrgExplorer

All issues in AOSSIE-Org/OrgExplorer

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.