Skip to content

add active SEP report task#6097

Draft
nks2109 wants to merge 2 commits intotrunkfrom
CU_868hxv4y0
Draft

add active SEP report task#6097
nks2109 wants to merge 2 commits intotrunkfrom
CU_868hxv4y0

Conversation

@nks2109
Copy link
Copy Markdown
Contributor

@nks2109 nks2109 commented Mar 18, 2026

PR Checklist

Please check if your PR fulfills the following requirements:

  • The title follows our guidelines
  • Tests for the changes have been added (for bug fixes/features), and they use let helpers and before blocks.
  • For all UI changes, there is Cucumber coverage.
  • Any endpoint touched in the PR has an appropriate Pundit policy. For open endpoints, the reasoning is documented in the PR and code.
  • Any endpoint modified in the PR only responds to the expected MIME types.
  • For all scripts or rake tasks, how to run them is documented in both the PR and the code.
  • There are no inline styles added.
  • There is no inline JavaScript added.
  • There is no hard-coded text added/updated in helpers/views/JavaScript. New/updated translation strings do not include markup/styles unless there is supporting documentation.
  • Code does not use .html_safe.
  • All images added/updated have alt text.
  • Does not bypass RuboCop rules in any way.

PR Type

What kind of change does this PR introduce?:

  • Bugfix
  • Feature (requires Feature flag)
  • Data fix, Migration, or Report (inert code, no impact until run)
  • Refactoring (no functional changes, no API changes)
  • Build related changes
  • CI related changes
  • Dependency updates (e.g., add a new gem or update to a version)
  • Release (Prepares code for a release, e.g., version bumps, changelog updates, tagging, deployment scripts)

What is the ticket # detailing the issue?

Ticket: https://app.clickup.com/t/868hxv4y0

A brief description of the changes:

Current behavior:

New behavior: Added a new active sep report rake task. It works based on the sep dates produced.

bundle exec rake reports:active_sep_report start_date="2026-01-01" end_date="2026-03-18"

Feature Flag

For all new feature development, a feature flag is required to control the exposure of the feature to our end users. A feature flag needs a corresponding environment variable to initialize the state of the flag. Please share the name of the environment variable below that would enable/disable the feature and indicate which client(s) it applies to.

Variable name:

  • DC
  • ME

Additional Context

Include any additional context that may be relevant to the peer review process.

@nks2109 nks2109 added the chore *️⃣ Some non-functional task that won't appear in release notes label Mar 18, 2026
@nks2109 nks2109 marked this pull request as draft March 19, 2026 18:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

chore *️⃣ Some non-functional task that won't appear in release notes do not merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant