Code-4-Community / Code-4-Community/bcan

Feature List

Open
#390 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2
Forks
0
PR merge metrics
No merged PRs in 30d

Description

Auth(Login/Sign up)

  • Login
  • Signup
  • Forgot Password
  • User Levels
    • Only employee or admin can see the full app
    • Inactive users have to approved
    • Only admin can see user and cashflow page
    • Auth cookies

Dashboard

  • Export CSV
  • Grants Applied to
  • Grants Received
  • Money Applied All Time
  • Money Received by Year
  • Money Captured
  • Average Amount
  • Success Rate by Year
  • Grant Status
  • Grant timeline

Grants

  • View all grants
  • Add Grant
  • Edit Grant
  • Delete Grant
  • Search for grants by name
  • Filter Grants
    • by status
    • by bcan eligibility
    • my grants(your email is the poc)
    • org name
    • due date
    • grant amount
    • status
  • Cost Benefit
  • Notifications
    • 1 day, 1 week, 3 week notifications for grants
    • Auto send updates to users emails
    • Grant documents
    • Grant POC(BCAN and non BCAN)

User Page

  • View Inactive users
  • View Active users
  • Change user role
    • Employee -> Admin
    • Admin - > Employee
  • Delete User
  • Approve inactive users
    • Email users when they are approved
  • Search for users

Cashflow

  • 36 month projection
  • Stats about Cashflow
    • Current Cash
    • Total Revenue
    • Monthly Cost
    • Annual Increases
    • Starting Cash Position and Date(editable)
    • Annual Salary and Benefit Increase(editable)
  • Revenue Items
    • Add Revenue
    • Edit Revenue
    • Delete Revenue
    • List out all Revenues
  • Cost
    • Add Cost
    • Edit Cost
    • Delete Cost
    • List all Cost

Settings

  • Change password
  • Profile pic
    • Upload profile pic
    • delete profile pic
    • show profile pic
  • Change user info
    • Email
    • First Name
    • Last Name

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No files, tests, or entry points are named. Start by reviewing the repository structure and splitting this broad list into separately scoped features with acceptance criteria; the work is done only when an agreed subset and its completion checks are defined.

Written by the indexing model from the issue text.

Assessment

Domain
full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.