Northeastern Electric Racing Project Management Dashboard - version 3

Overview

FinishLine by NER

Also known as PM Dashboard v3.

A project management web application built in Typescript, React, and Express.

Almost all of our documentation is on our Confluence page. Start there to learn what the project is all about.

All questions can be directed to #software in the NER Slack (backup contact: @anthonybernardi).

Environment Setup for Developers Who Worked on v2

If you worked on PM Dashboard v2, then setting this up will be easy. Here are the steps:

  1. make sure you have the database running like in pm-dashboard-v2
  2. get the same .env file from pm-dashboard-v2 but put it in src/backend/
  3. npm install -g yarn
  4. yarn install
  5. yarn prisma:reset
  6. yarn start

Note: no more npm commands! Any time you would run npm run ... run yarn ... instead!

Environment Setup for New Developers

We have redone our onboarding docs and moved them to Confluence! Check them out here. If you have questions, ask them in the #software_env-setup channel in Slack. When you're done, check out the contributor guide (see below).

How to Contribute

Check out the contributor guide. This will take you through the steps of finding a ticket, making a branch, committing code, creating a pull request, etc!

Comments
  • General - Research libraries for redesigning our form architecture

    General - Research libraries for redesigning our form architecture

    Desired Changes

    As of now, we currently use states and pass those down to the view components to get the data from our forms and then send them back up to our container component to do business logic with them/pass the data to our custom react hooks. We also manually do form validation, and our current validation is the bare minimum at best. We want to utilize existing libraries that provide the tools and architecture that would allow us to create flexible forms with proper validation and are easy to build. Some potential options we have right now are Formik and React Hook Forms.

    Screenshots (as needed)

    No response

    feature enhancement technical improvement spike 
    opened by jpwaves 13
  • General - Diagram out our data entities and relationships

    General - Diagram out our data entities and relationships

    Spike Type

    Functional

    Goal

    Model out what our database and entities look like

    Reason for Spike

    So our devs can have an understanding about what our data is and how they are connected to each other. This may also spark discussions about how to better improve our current structure for our data.

    Additional notes

    Needs an ERD made

    spike 
    opened by jpwaves 10
  • #142 MUI migration -- forms

    #142 MUI migration -- forms

    Changes

    Migrate a shit ton of forms to MUI

    Notes

    I think I folded in LocalizationProvider, I forget

    Screenshots (if applicable)

    I should add

    Checklist

    It can be helpful to check the Checks and Files changed tabs. Please review the contributor guide and reach out to your Tech Lead if anything is unclear. Please request reviewers and ping on slack only after you've gone through this whole checklist.

    • [x] All commits are tagged with the ticket number
    • [x] No linting errors
    • [x] No newline at end of file warnings
    • [x] All code follows repository-configured prettier formatting
    • [x] No merge conflicts
    • [x] All checks passing
    • [x] Screenshots of UI changes (if applicable)
    • [x] Remove any non-applicable sections of this template
    • [x] Assign the PR to yourself
    • [x] PR is linked to the ticket
    • [x] No yarn.lock changes (unless dependencies have changed)
    • [x] Request reviewers & ping on Slack

    Closes #142

    opened by jamescd18 9
  • #181: Add teams page

    #181: Add teams page

    Changes

    Made teams page have expandable team thingies like for the work packages on the projects page. The info is a little sparse on it ngl but idk what else to add

    Screenshots (if applicable)

    image

    Closes #181

    opened by anthonybernardi 8
  • General - Research structure for front end organization and make write-up of front-end practices

    General - Research structure for front end organization and make write-up of front-end practices

    Spike Type

    Technical

    Goal

    Improve the organization of front-end components and overall project structure for things related to front-end, and create a wiki or docs page listing out what practices and style we want to use for all our front-end files.

    Reason for Spike

    To standardize our practices so it's easier for new devs to onboard and all our code follows best practices (to some extent)

    Additional notes

    may need to look into how we want to also test front-end components too and make a doc on that

    spike 
    opened by jpwaves 8
  • Change Request - Notify users when a CR is submitted

    Change Request - Notify users when a CR is submitted

    Overview

    Send a Slack message in the relevant channel when a change request is submitted, thereby increasing timely visibility of change requests.

    Original request from Nick DePatie

    Push notification system for users to be notified when they need to review a CR

    Stakeholders

    Product Stakeholder: @jamescd18 Engineering Stakeholder: @RChandler234 Reference Users: Nick DePatie, Anushka Wani

    User Story

    As an Engineering Head, I want to know in a timely manner when a change request is submitted for a project on my team so that I can see it, discuss it, and review it all without substantial delay.

    Success Metrics

    Success will be measured based on timely change request viewership. This feature directly addresses data visibility issues, so we want to see this drive increased interactivity with change requests in FinishLine.

    We can measure this by recording the timestamps for specific user behaviors before and after this feature is built, and compare the deltas between specific user behavior timestamps.

    1. When a change request is submitted
    2. When someone other than the user that submitted the change request first views the change request
    3. When the user that ultimately reviews the change request first views the change request

    This feature will be successful if the average duration from point 1 to point 2 and point 1 to point 3 can be meaningfully reduced. These two durations being relatively short would represent positive interactivity with FinishLine change requests and the change management system.

    Point 1 to Point 2 Current Average: (on based on <# of CRs> from X_DATE to Y_DATE) Point 1 to Point 3 Current Average: (on based on <# of CRs> from X_DATE to Y_DATE)

    A fun bonus user satisfaction proxy metric can be Slack message reactions. Slack message reactions are a fairly good measure of user interactivity with a message. On average, how many users are reacting to the Slack messages? On average, how many unique reactions does each message get?

    Rollout Plan

    • Deployment to production: immediate, ideally no database impact
    • Survey reference users for qualitative feedback

    Out of Scope

    • Changes to anything with the change request data model

    Background / Context

    Currently, nothing automated happens when a change request is submitted. Whoever submits a change request must separately and manually write and send a Slack message after submitting the change request to ask people to review them.

    Prerequisites

    • Teams data model built with Slack channel ID and webhook URL stored

    Acceptance Criteria & Mock-ups

    When a change request is submitted, send a Slack message in the following format:

    @<TEAM_HEAD> <CR_TYPE> Change Request #<CR_ID> was just submitted by @<SUBMITTER>
    

    The text #<CR_ID should be a link to the change request’s page. An example is shown below:

    “@ Nick DePatie STAGE_GATE Change Request #1234 was just submitted by @ Anushka Wani”

    The Slack message should be sent in the channel for the team who’s project the change request is the subject of. In other words, find the appropriate channel by tracing change request > wbs element > project > team > channel.

    Implementation Notes

    We previously built a Slack app for the NER PM Dashboard v0, which can be used for rough testing / exploring by contacting @jamescd18. Messages being sent in channels are done ~via web hooks, and a new web hook must be created for each channel in which the to-be-built FinishLine Slack bot user will be sending messages~.

    ~Creating the bot’s web hook for a given channel will provide a web hook URL in the following pattern. https://hooks.slack.com/services/<SLACK_TEAM_ID>/<WEBHOOK_PART_A>/<WEBHOOK_PART_B> Slack team ID should ideally be stored as a tenant / organization setting, but I don’t think that should be a prerequisite for this ticket. The two parts of the web hook unfortunately don’t match the channel ID, so they could either be stored as two separate database variables or put together as one variable with the slash included.~

    See https://api.slack.com/messaging/sending

    back-end difficult new feature 
    opened by nwdepatie 5
  • #233 - Update Risk Permissions

    #233 - Update Risk Permissions

    Changes

    • Changed logic for Create Risk button - only shows up if a user is not a guest
    • Changed logic for delete button - disabled if you don't have permissions AND if you didn't create the risk

    Notes

    • This can be tested by commenting out one of the roles in hasPermissions, then going into that role and creating a risk, switching roles to check off the risk, and then going back to the original role and deleting said risk (while seeing that other risks are disabled)

    Test Cases

    • Create Risk button does not show up if you're a guest
    • Delete button is not disabled if you created the risk but don't have permissions

    Screenshots

    • Nothing really new, self explanatory but can provide if needed

    To Do

    • [ ] Make tests

    Checklist

    It can be helpful to check the Checks and Files changed tabs. Please review the contributor guide and reach out to your Tech Lead if anything is unclear. Please request reviewers and ping on slack only after you've gone through this whole checklist.

    • [ ] All commits are tagged with the ticket number
    • [x] No linting errors / newline at end of file warnings
    • [x] All code follows repository-configured prettier formatting
    • [x] No merge conflicts
    • [x] All checks passing
    • [x] Screenshots of UI changes (see Screenshots section)
    • [x] Remove any non-applicable sections of this template
    • [x] Assign the PR to yourself
    • [x] No yarn.lock changes (unless dependencies have changed)
    • [x] Request reviewers & ping on Slack
    • [x] PR is linked to the ticket (fill in the closes line below)

    Closes #233

    opened by z-roth 4
  • #98 - Implement try/catch responses in controllers

    #98 - Implement try/catch responses in controllers

    Changes

    There are two places TypeError shows up:

    1. In functions like createWorkPackage(req, res) that have Express responses. In these cases the fix is straightforward: replace TypeError with the appropriate res.status(40X). This is done in commit https://github.com/Northeastern-Electric-Racing/FinishLine/commit/dad227a34e7d0191fdc6273d8ab15cb3468a554c
    2. In transformers like userTransformer(user) that return JSON data representing the user. This is either embedded within other transformers or sent to a controller that returns a response. So our course of action is to track all transformers that rely at some point on userTransformer (the other problematics teamTransformer and projectTransformer also rely on userTransformer) and try/catch TypeErrors to return the appropriate response.

    Notes

    What if we treated all transformers as risky and not just the ones with userTransformer? This would make things more robust. All transformers except authenticatedUserTransformer rely on (and propagate errors from) userTransformer anyway. (authenticatedUserTransformer is only ever used in logUserIn(req, res), so you can add the 400 error in there if you want).

    We did not touch the transformers in src/frontend/src/apis, as they do not throw new TypeError.

    Test Cases

    No tests yet. :( (Merging to working branch)

    To Do

    Not sure how necessary these are. None of them are required for this fix to work.

    • [ ] abstract out a helper function tryUserTransformer(res, succResCode, failResCode) (there was a lot of copy/paste here!)
    • [ ] resolve res.status vs return res.status, which is currently inconsistent (find and replace try { res vs try { return res)
    • [ ] as in the Notes, be extra cautious and add the try/catch to authenticatedUserTransformer too.

    Checklist

    It can be helpful to check the Checks and Files changed tabs. Please review the contributor guide and reach out to your squad if anything is unclear. Please request reviewers and ping on slack only after you've gone through this whole checklist.

    • [x] All commits are tagged with the ticket number
    • [ ] No linting errors
    • [ ] No newline at end of file warnings
    • [x] All code follows repository-configured prettier formatting
    • [x] No merge conflicts
    • [ ] All checks passing
    • [x] Screenshots of UI changes (if applicable)
    • [x] Remove any not-applicable sections
    • [x] Assign the PR to yourself
    • [x] PR is linked to the ticket
    • [x] No package-lock.json changes (unless dependencies have changed)
    • [x] Request reviewers & ping on Slack
    opened by jonathan-chen10 4
  • MUI/ - messing with the MUI button

    MUI/ - messing with the MUI button

    Changes

    Testing out MUI with a couple of components starting with the Action-Button.

    Notes

    Planning to continue transitioning files from react-bootstrap to MUI using this PR, wanted to get it up for visibility.

    Screenshots (if applicable)

    MUI Button: image Old Button: image

    To Do

    Transitioning the rest of the react-bootstrap stuff, will compile a list here.

    Checklist

    It can be helpful to check the Checks and Files changed tabs. Please review the contributor guide and reach out to your squad if anything is unclear. Please request reviewers and ping on slack only after you've gone through this whole checklist.

    • [ ] All commits are tagged with the ticket number
    • [ ] No linting errors
    • [ ] No newline at end of file warnings
    • [ ] All code follows repository-configured prettier formatting
    • [ ] No merge conflicts
    • [ ] All checks passing
    • [ ] Screenshots of UI changes (if applicable)
    • [ ] Remove any not-applicable sections
    • [ ] Assign the PR to yourself
    • [ ] PR is linked to the ticket
    • [ ] No package-lock.json changes (unless dependencies have changed)
    • [ ] Request reviewers & ping on Slack

    Closes # (issue #)

    opened by RChandler234 4
  • Work Packages - Investigate Alternate Gantt Chart Packages

    Work Packages - Investigate Alternate Gantt Chart Packages

    Spike Type

    Technical

    Goal

    Our goal is to switch over our existing Gantt chart package. At the successful conclusion of this epic, our work package Gantt charts will be swapped over to a selected new react package. No functionality will be lost, and Display dates will be changed from Sundays to Mondays. This package will be recorded as the new standard for our Gantt charts moving forwards

    Reason for Spike

    As brought up by James and Anthony, we aren't too satisfied with the defacto bootstrap Gantt chart package we have been using. It isn't very intuitive and hard to customize for our needs. As such, we need to swap from it.

    Additional notes

    We have some packages that Anthony has initially identified in React;

    medium front-end spike 
    opened by leoRysing 4
  • Change Requests - Implemented Changes List Has Incorrect WBS Numbers

    Change Requests - Implemented Changes List Has Incorrect WBS Numbers

    Browser(s)

    Firefox

    Platform(s)

    Desktop

    Version(s)

    main

    Observed Behavior

    The linked WBS numbers for each implemented change displays the incorrect WBS number for some projects and work packages.

    Expected Behavior

    The WBS numbers linked for each implemented change should route to the correct project/work package and also display the correct WBS number for each as well.

    Steps to Reproduce

    1. Create a new work package or project
    2. Go to the change request details page associated with the newly created work package/project
    3. Compare the WBS Numbers in the Implemented Changes list to those stored in your database

    Technical Notes

    Code in question is located in backend/functions/change-requests.ts, specifically these lines: https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/blob/d7ab161dc51d936a5cb5a9ac3f05c40cfaee3b25/src/backend/functions/change-requests.ts#L73-L76 We should not be reusing the wbsNum we defined previously here as that refers to the WBS Element that the change request is linked to, which is different from the wbsNum for each individual change (each change could refer to a different work package or project than the change request itself is linked to).

    Screenshots (as needed)

    bugged-wbsnums1 bugged-wbsnums2

    bug back-end straightforward 
    opened by jpwaves 4
  • #487: Refactor Description Bullets

    #487: Refactor Description Bullets

    Changes

    Separated controller function into service and turn into a class. threw new exceptions accordingly moved transformer and args to new files

    Checklist

    It can be helpful to check the Checks and Files changed tabs. Please review the contributor guide and reach out to your Tech Lead if anything is unclear. Please request reviewers and ping on slack only after you've gone through this whole checklist.

    • [x] All commits are tagged with the ticket number
    • [x] No linting errors / newline at end of file warnings
    • [x] All code follows repository-configured prettier formatting
    • [x] No merge conflicts
    • [x] All checks passing
    • [x] Screenshots of UI changes (see Screenshots section)
    • [x] Remove any non-applicable sections of this template
    • [x] Assign the PR to yourself
    • [x] No yarn.lock changes (unless dependencies have changed)
    • [x] Request reviewers & ping on Slack
    • [x] PR is linked to the ticket (fill in the closes line below)

    Closes #487

    opened by ryanhowe28 0
  • 462 typography consistency box/grid

    462 typography consistency box/grid

    Changes

    Typography Tags Added Where Applicable

    Notes

    I have no idea how I was supposed to add the styling functions, so I just made its own folder and file and imported where needed but if I received feedback on where/how to introduce that, it would be very helpful.

    To Do

    Sort of explained above, but fixing that and also I need to fix imports for consistency, but Ill do that later after the meat of the ticket is fixed.

    Closes #462

    opened by nezamj03 0
  • #373 newProject accounts for team

    #373 newProject accounts for team

    Changes

    Made a check to see if the request body includes teamId. If it does not include teamId, a project is similarly created without any teamId, but if it is provided, it verifies for a valid teamId and if it is not, it will send a 404. if it is, it will create the project with the teamId.

    Notes

    n/a

    Test Cases

    passed all tests

    To Do

    require a teamId in order to not check for an unprovided one.. transition to requiring teamIds

    Closes #373

    opened by nezamj03 0
  • #486 users backend refactoring

    #486 users backend refactoring

    Notes

    This is me taking a first pass at this based on what I saw in the risks PR. There are definitely some places where I need some help(what to return for updateUserSettings and verification I'm doing the userLogin ones correctly). I'm not really sure what you meant by #7 in the ticket, I wasn't sure where the userId was a param I shouldn't change/ where it's a userId I should replace with the auth userId. Also I still need to do the test stuff, but wanted to get what I have done up first.

    To Do

    Update user tests and user test data

    Checklist

    It can be helpful to check the Checks and Files changed tabs. Please review the contributor guide and reach out to your Tech Lead if anything is unclear. Please request reviewers and ping on slack only after you've gone through this whole checklist.

    • [x] All commits are tagged with the ticket number
    • [x] No linting errors / newline at end of file warnings
    • [x] All code follows repository-configured prettier formatting
    • [x] No merge conflicts
    • [ ] All checks passing
    • [x] Screenshots of UI changes (see Screenshots section)
    • [x] Remove any non-applicable sections of this template
    • [x] Assign the PR to yourself
    • [x] No yarn.lock changes (unless dependencies have changed)
    • [x] Request reviewers & ping on Slack
    • [x] PR is linked to the ticket (fill in the closes line below)

    Closes #486

    opened by RChandler234 0
  • General - MUI Upgrades

    General - MUI Upgrades

    Overview

    With the introduction of MUI as our front-end framework, a number of different functionality upgrades are possible with new and more powerful components available in MUI. Where it makes sense, we should undertake upgrades to enhance the user experience.

    Tickets

    • [ ] add quick filter to toolbar
    • [ ] add custom filter operators
    • [ ] add project row actions
    • [ ] add change request row actions
    epic 
    opened by jamescd18 0
  • #369 - added hopefully working endpoint and wrote two successful tests

    #369 - added hopefully working endpoint and wrote two successful tests

    Changes

    I essentially added test data and created an endpoint for team descriptions. I added test data so that things could be tested and made a method that allows for users to edit the team description.

    Notes

    There's a chance that the projects test data is broken since it doesn't reference an existing WBS element. That error held me back for quite a bit on this ticket.

    Test Cases (SO FAR)

    • Case A: Everything works normally
    • Case B: Fails when invalid perms

    To Do

    Just needs to be transferred over to a user who can complete the testing so that the ticket doesn't block anymore.

    Checklist

    • [ ] All commits are tagged with the ticket number
    • [ ] No linting errors / newline at end of file warnings
    • [ ] All code follows repository-configured prettier formatting
    • [ ] No merge conflicts
    • [ ] All checks passing
    • [x] Screenshots of UI changes (see Screenshots section)
    • [ ] Remove any non-applicable sections of this template
    • [ ] Assign the PR to yourself
    • [x] No yarn.lock changes (unless dependencies have changed)
    • [ ] Request reviewers & ping on Slack
    • [ ] PR is linked to the ticket (fill in the closes line below)

    Closes #369

    opened by sho-r1024 0
Releases(v3.5.0)
  • v3.5.0(Dec 16, 2022)

    Notes

    We got MUI done! This was a big project and completely changes the look of the website and also what we can do with it.

    Auto Generated:

    • #142 MUI migration of themes by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/176
    • MUI migration -- data grid by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/175
    • MUI migration -- top bar by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/177
    • MUI migration - convert card components by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/180
    • #142: MUI top bar and other stuff by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/306
    • #142 MUI migration -- forms by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/218
    • #142 MUI MERGE by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/341
    • Add NER Button by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/347
    • #142: MUI - teams and user settings by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/349
    • #142 MUI migration rishav by @rishavsarma5 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/348
    • #142 - Jonathan's MUI migrations by @jonathan-chen10 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/351
    • #276 - Converted Project Actions Button from Boostrap to MUI by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/381
    • #279 - Change Checklist Icons from FontAwesome to MaterialUI by @zachnorman02 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/378
    • #142 m UI migration reid 2 by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/350
    • #401 activate work package modal m UI by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/408
    • #392 mui reviewchangerequestview by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/407
    • #280: Changed to MUI Button. Uses NER attributes, but cannot use NERButton. by @nezamj03 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/427
    • #397 m UI work packages by timeline status by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/430
    • #402 mui stage gate work package modal by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/431
    • #400: Project Edit Form by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/424
    • #265: Added 2 tests for createWorkPackage by @akale22 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/416
    • #409 Allow project leads to check description bullets by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/413
    • #395 - remove react bootstrap change request table by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/442
    • #436 mui edit mode options by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/441
    • #433 - remove action button mui by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/440
    • #258: Make a command to run prisma studio by @akale22 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/451
    • #435 - Transition Risk Log to MUI by @z-roth in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/450
    • 356-created-sendSlackCRReviewNotification by @ryanhowe28 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/374
    • #388, #389, #390, #391, #396 - MUI Proposed Solutions by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/423
    • #385 - Transition to MUI WbsStatus.tsx by @jonathan-chen10 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/444
    • #165: Renaming API Files by @nezamj03 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/453
    • #443 - New fonts in MUI for new club style by @jonathan-chen10 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/461
    • #103 Make PageBlock Collapsable by @z-roth in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/460
    • #142 StandardDetails & StageGateDetails by @joshiarnav in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/449
    • #455: MUI Create CR Form by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/456
    • work package edit form by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/454
    • #288 add project name to work package type by @ryanhowe28 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/465
    • #122-calculated-projects-status-automatically-based-on-its-work-packa… by @callmejim1226 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/412
    • #386 Transition Sidebar to MUI by @z-roth in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/474
    • #244 Test editRisk endpoint successes by @jaredlyon in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/330
    • #468: Add All Frontend Features by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/471
    • #463: fix mui tests by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/475
    • Major UI Revamp w/ MUI Migration by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/174
    • #445: refactoring some of the risks stuff by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/446
    • #195 work package progress for Stage Gate CRs by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/452
    • #190 Unchecking Confirm by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/479
    • #187 - Added WPP Tooltip by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/483
    • #371: Set Project Team Endpoint by @Danwo0 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/472
    • #359 W TeamsSpecificPage by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/478
    • #168: renames frontend util files by @andrewstsai in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/426
    • #469 - cleanup small details on frontend by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/480

    New Contributors

    • @nezamj03 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/427
    • @akale22 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/416
    • @jaredlyon made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/330
    • @andrewstsai made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/426

    Full Changelog: https://github.com/Northeastern-Electric-Racing/FinishLine/compare/v3.4.0...v3.5.0

    Source code(tar.gz)
    Source code(zip)
  • v3.4.0(Nov 11, 2022)

    What's Changed

    • #342: dev login is better now by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/343
    • Replaced all PM-Dashboard-v2 in the license statements of backend .ts files to FinishLine by @rombuski in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/329
    • #25: end date calculation of logic moved to back-end by @jinhyunh in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/297
    • #286 move start date calculation to backend by @callmejim1226 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/355
    • #264 backend test CreateWorkPackage endpoint part 2 by @anurag-arasan in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/318
    • #262-tested-update-user-settings by @ryanhowe28 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/353
    • #310 adjusted the crId field in project edits to be empty instead of -1 by @ethankong150 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/328
    • #48 Add custom sorting for durations by @dli85 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/361
    • #252 test getSingleProject endpoint by @a-geng in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/364
    • #375: applying prettier formatting by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/376
    • #219-added-two-tests-for-getUserSettings by @rishavsarma5 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/366
    • #192 - Fix Work Package Edit Form, Remove Progress from Backend by @z-roth in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/367
    • #379-calculated-WP-progress-if-no-bullets by @ryanhowe28 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/382
    • #251: Tried testing getAllProjects endpoint by @vitakh in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/384
    • #325 - If a Work Package is not active then as per the UI checkboxes … by @sho-r1024 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/404
    • #311: Move Validator to Utils.ts by @Danwo0 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/383
    • #338-Automate-Implementation-for-proposed-solutions by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/377
    • #336 Sort items before passing to checklist by @ameall in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/406
    • #22: Add text wrapping to Change Requests table by @zachnorman02 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/410
    • #9: J W T by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/357
    • #21- Add text wrapping to Projects table by @zachnorman02 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/411
    • #414 - More Auth by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/417

    New Contributors

    • @jinhyunh made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/297
    • @anurag-arasan made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/318
    • @dli85 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/361
    • @a-geng made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/364
    • @vitakh made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/384
    • @ameall made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/406

    Full Changelog: https://github.com/Northeastern-Electric-Racing/FinishLine/compare/v3.3.0...v3.4.0

    Source code(tar.gz)
    Source code(zip)
  • v3.3.0(Oct 16, 2022)

    What's Changed (auto generated, may or may not contain some duplicate stuff from last release)

    • #263 Created two tests for work-packages by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/275
    • #15- moved packages beginning with @types/ by @NoelleMarcel in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/298
    • #233 - Update Risk Permissions by @z-roth in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/304
    • #161: Added abstraction and changed routes by @leshemo in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/285
    • #289 hid add proposed solution button for guests by @rycheung10 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/302
    • #253: Write tests for createRulesChangesJson by @zachnorman02 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/301
    • Update favicon.ico by @rombuski in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/307
    • #294: Better Frontend Testing by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/295
    • #186 - WPP CheckList by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/305
    • #194 add description bullet post endpoint by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/303
    • #167: changed all stylesheet file names to kebab case by @ethankong150 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/235
    • #166: renamed hook files to lowercase by @thomaskummer1 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/299
    • #204: Fixing Dates by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/309
    • #224 - Added slackId parameter to User_Settings + updateUserSettings by @sho-r1024 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/267
    • 322: Prisma Migrate DB on Deploy by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/324
    • #189: Checklists Drive Progress Wire Up by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/316
    • #107 - Checklists Drive Progress by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/308
    • #287: Ran commands to change dependency by @leshemo in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/327
    • #232: Make Risks Less Restrictive by @Danwo0 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/321
    • #226: added and implemented helper print function by @stevenl224 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/319
    • #331 - disable buttons by @RChandler234 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/332
    • #225 frontend set slack id by @glacierA in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/261
    • #292 Created Role Changing Endpoint by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/317
    • #339: desc bullet migration script by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/340

    New Contributors

    • @z-roth made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/207
    • @tigerhippo made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/217
    • @sho-r1024 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/209
    • @stevenl224 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/234
    • @Peyton-McKee made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/257
    • @jonathan-chen10 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/227
    • @ryanhowe28 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/254
    • @joshiarnav made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/269
    • @NoelleMarcel made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/298
    • @leshemo made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/285
    • @rycheung10 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/302
    • @zachnorman02 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/301
    • @rombuski made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/307
    • @ethankong150 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/235
    • @thomaskummer1 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/299
    • @RChandler234 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/332
    Source code(tar.gz)
    Source code(zip)
  • v3.2.0(Oct 5, 2022)

    Readable Changes

    Proposed Solutions

    • All standard change requests now have a list of “proposed solutions”
    • A proposed solution has: description, scope impact, budget impact, and timeline impact
    • To be able to approve a change request, you will have to select a proposed solution to be approved for that change request
    • You can make the proposed solutions while creating the CR or after
    • This allows you to make a change request just to identify a problem. Then you can come up with the solutions as needed and reviewers can wait until there’s an adequate solution to approve
    • Thanks to Reid, Arnav, Ari, Ji-min, and Jun (also me lol) for working on this! This was a big one

    Other Changes

    • Approving a stage gate CR will automatically update the wp's status to complete and it’s progress to 100% (thanks Megan)
    • Approving an activation CR will automatically update the wp's status to be active and it’s start date and lead/manager to be what’s on the CR (thanks me lol)
    • If you don’t have permissions to edit or delete a risk, then it will just show up as bullets (thanks Zack)
    • The teams page now lists every team that exists as well as their projects and members
    • You can now edit a CR’s project/work package right from the “Implement CR” dropdown! It even autofills the crId for you :D (ty for the request Anushka)

    What's Changed

    • #206 - Added permissions and ability to view risks as bullets by @z-roth in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/207
    • #72: Auto implement Activation CR by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/198
    • #87: modifed endpoint for approving change requests by @Danwo0 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/183
    • #83 - Display Page Proposed Solutions Visual by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/191
    • #220: Pull Request Template by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/221
    • #132: updating issue templates by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/222
    • #73 Auto-Implement Approved Stage Gate CR by @tigerhippo in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/217
    • #98 backend errors 4xx by @sho-r1024 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/209
    • #181: Add teams page by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/182
    • #86 wire up n proposed solutions by @callmejim1226 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/215
    • #169: Renamed TestSupport files to kebab case by @stevenl224 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/234
    • #82 - Added ProposedSolutionsList to CreateCRPage by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/211
    • #236: better backend jest practices by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/237
    • #229 Update Cookies Disclaimer by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/257
    • #163: Add Proposed Solution Seed Data by @Danwo0 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/216
    • #89 - Select Proposed Solution on Review Form by @glacierA in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/208
    • #139- Renamed seed files by @ryanhowe28 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/254
    • #162 Create Validation Statement by @Peyton-McKee in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/256
    • #212 remove scope timeline budget by @joshiarnav in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/269
    • #281: wbs edit from change request page by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/282
    • #86: Wiring Up by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/283
    • #80 - Proposed Solutions by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/210

    New Contributors

    • @z-roth made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/207
    • @tigerhippo made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/217
    • @sho-r1024 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/209
    • @stevenl224 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/234
    • @Peyton-McKee made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/257
    • @ryanhowe28 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/254
    • @joshiarnav made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/269
    Source code(tar.gz)
    Source code(zip)
  • v3.1.1(Sep 15, 2022)

    Changes

    • The risk log is finished and now fully functional! Thanks Zack and Ari!
    • Ari added Calendar links to the info page
    • More behind the scenes stuff that brings us closer to releasing even more features
    Source code(tar.gz)
    Source code(zip)
  • v3.0.5(Sep 3, 2022)

    Main / Finished Things

    • Kevin fixed project duration calculation
    • Ji-min moved the WPs block to be above the changes block
    • Anthony added version number in the bottom left corner
    • Anthony and James fixed a bunch of random little things
    • James added Slack notifications for newly submitted change requests
    • Anthony added some pre-fill for the new WP form

    What's Changed

    • #24-now-uses-proper-duration-util-function by @glacierA in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/147
    • #149 Make WPs block appear above the changes block in projects page by @callmejim1226 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/152
    • #100: what does this ticket even mean by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/155
    • #18: added version number to settings page by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/154
    • #131: Reset script is os agnostic by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/156
    • #158: changed the docs by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/159
    • #85: Proposed Solution schema changes by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/150
    • #170 - Apply prettier formatting by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/171
    • #77 submit cr slack notification by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/146
    • #172 - create baseline manual script for PM stats pull by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/173
    • #35: Create new WP Query Params by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/179

    New Contributors

    • @callmejim1226 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/152

    Full Changelog: https://github.com/Northeastern-Electric-Racing/FinishLine/compare/v3.0.4...v3.0.5

    Source code(tar.gz)
    Source code(zip)
  • v3.0.4(Aug 22, 2022)

    What's Changed

    • #128 - update test to FinishLine by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/129
    • #125 fix prettier configs by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/127
    • #124 - updated home page to fix scroll by @jamescd18 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/126
    • #52 stop self reference in dependency wp by @glacierA in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/117
    • #133 - moving the risk log below summary above gantt chart by @leoRysing in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/137
    • #84 - Created Individual Proposed Solution Form by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/130
    • #69: Edit Risk Endpoint by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/145
    • #138: iykyk by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/140
    • #67: Delete Risk Endpoint by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/144

    New Contributors

    • @jamescd18 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/129
    • @leoRysing made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/137

    Full Changelog: https://github.com/Northeastern-Electric-Racing/FinishLine/compare/v3.0.3...v3.0.4

    Source code(tar.gz)
    Source code(zip)
  • v3.0.3(Aug 16, 2022)

  • v3.0.2(Aug 16, 2022)

    v3.0.2

    This is just hotfixes to get the deployment running

    What's Changed

    • #108 - css by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/109
    • #110 - added scripts by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/111
    • #6 - Updated tsconfig.build.json by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/8
    • added integer checks for budget and timeline impact inputs by @glacierA in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/113
    • #3 - moving hooks and apis out by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/4
    • #114 removed expected progress and timeline status from project-details by @Danwo0 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/118
    • #115 - Duplicate File Names by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/116
    • #66 - Risk Create Endpoint by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/121
    • #119: better validation by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/120

    New Contributors

    • @anthonybernardi made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/109
    • @Ari-S-123 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/8
    • @glacierA made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/113
    • @Danwo0 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/118

    Full Changelog: https://github.com/Northeastern-Electric-Racing/FinishLine/compare/v3.0.1...v3.0.2

    Source code(tar.gz)
    Source code(zip)
  • v3.0.1(Aug 15, 2022)

    WELCOME TO V3!

    This is now v3 of the dashboard and is the new official deployment. It is also now called FinishLine by NER. This is the first release of it! Woo!

    What's Changed

    • #108 - css by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/109
    • #110 - added scripts by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/111
    • #6 - Updated tsconfig.build.json by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/8
    • added integer checks for budget and timeline impact inputs by @glacierA in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/113
    • #3 - moving hooks and apis out by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/4
    • #114 removed expected progress and timeline status from project-details by @Danwo0 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/118
    • #115 - Duplicate File Names by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/116
    • #66 - Risk Create Endpoint by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/121
    • #119: better validation by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/120

    New Contributors

    • @anthonybernardi made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/109
    • @Ari-S-123 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/8
    • @glacierA made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/113
    • @Danwo0 made their first contribution in https://github.com/Northeastern-Electric-Racing/FinishLine/pull/118

    Full Changelog: https://github.com/Northeastern-Electric-Racing/FinishLine/commits/v3.0.0

    v2 Release Notes

    What's Changed

    • #738 components from pipes by @jamescd18 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/751
    • #727 manual database insertion by @jamescd18 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/753
    • #737 abstract card by @jamescd18 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/752
    • #698 - edit schema by @RChandler234 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/721
    • #555-updated implemented changes section through back end where it n… by @callmejim1226 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/692
    • #662 - Removed forced page reloads by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/762
    • #554 changed 'wbs element status' to 'status' in the work-packages-edit.ts… by @tigerhippo in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/760
    • #406 - Logout Button Not Working by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/763
    • #666 - Removed the spread operator wherever it appeared in the code by @tigerhippo in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/747
    • #765 remove empty css files by @RChandler234 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/766
    • #662 - Fixed Project Details Re-render by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/775
    • #767 - Risks.ts file and getRisks by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/768
    • #730 add user settings by @jamescd18 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/757
    • #732 - Teams by @anthonybernardi in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/754
    • #770 - Moved stylesheets to appropriate places and refactored imports by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/776
    • #780 prisma manual scripts by @jamescd18 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/781
    • #696 create risk log visuals by @z-roth in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/769
    • #771 - Moved Frontend Test Files by @Ari-S-123 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/782
    • #777 realign editable bullets by @Danwo0 in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/792

    New Contributors

    • @callmejim1226 made their first contribution in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/692
    • @tigerhippo made their first contribution in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/760
    • @Danwo0 made their first contribution in https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/pull/792

    Full Changelog: https://github.com/Northeastern-Electric-Racing/PM-Dashboard-v2/compare/v2.2.3...v2.2.4

    Source code(tar.gz)
    Source code(zip)
Owner
Northeastern Electric Racing
Northeastern Electric Racing
Dashboard skeleton Simple and fast dashboard skeleton template

Dashboard skeleton Simple and fast dashboard skeleton template. Installation npm install --save dashboard-skeleton-compostrap Version 1x built on Boo

Compostrap 9 Aug 23, 2022
The Frontend of Escobar's Inventory Management System, Employee Management System, Ordering System, and Income & Expense System

Usage Create an App # with npx $ npx create-nextron-app my-app --example with-javascript # with yarn $ yarn create nextron-app my-app --example with-

Viver Bungag 4 Jan 2, 2023
The Remix version of the fakebooks app demonstrated on https://remix.run. Check out the CRA version: https://github.com/kentcdodds/fakebooks-cra

Remix Fakebooks App This is a (very) simple implementation of the fakebooks mock app demonstrated on remix.run. There is no database, but there is an

Kent C. Dodds 61 Dec 22, 2022
A great result management solution for schools, hospital, academy and other. If you are a php developer, contribute to this respository for more advancement of the project.

result-management-pro A great result management system for schools, hospital, academy and more. Contributions Willing to add more features to this gre

Adeleye Ayodeji 8 Jun 17, 2022
The project integrates workflow engine, report engine and organization authority management background, which can be applied to the development of OA, HR, CRM, PM and other systems. With tlv8 IDE, business system development, testing and deployment can be realized quickly.

介绍 项目集成了工作流引擎、报表引擎和组织机构权限管理后台,可以应用于OA、HR、CRM、PM等系统开发。配合使用tlv8 ide可以快速实现业务系统开发、测试、部署。 后台采用Spring MVC架构简单方便,前端使用流行的layui界面美观大方。 采用组件开发技术,提高系统的灵活性和可扩展性;采

Qian Chen 38 Dec 27, 2022
🏆Open source, free project management/issue tracking software to manage your work and projects

WorkClever ?? Open source, free project management/issue tracking software to manage your work and projects Features General Free to use, open source

WorkClever 11 Dec 27, 2022
A "to-do" list management project

To-do List This project is about creating a functionable to-do list Built With HTML CSS Javascript Linters for html&css and js Webpack ES6 classes Web

Lucas Mullen 5 Sep 1, 2022
Gthub action for Project (beta) management. Allows to update fields

titoportas/update-project-fields Use this action to automatically update GitHub project (beta) item fields. Note that this action does not support Git

null 3 Nov 3, 2022
A complete COVID-19 tracker cum dashboard website made by me.

Covidview A detailed dashboard of live COVID-19 cases. Techs Used: React JS React Hooks and DOM Firebase WHO disease API Demo Video : covid.mp4 Workin

MAINAK CHAUDHURI 24 Dec 17, 2022
A simple dashboard to keep track of all your active devices/servers

Slashboard Pulsar A lightweight node js app designed to work with the Slashboard desktop client Built using Node.js Installation Clone this repository

Philippe Négrel-Jerzy 25 Dec 21, 2022
A dashboard for managing orders and inventory for a wordpress e-commerce site which has woo commerce plugin installed

WordPressWooCommerceDashboard - A dashboard for managing orders and inventory for a wordpress e-commerce site which has woo commerce plugin installed. This program provides shipping tracking for Delhivery.

Vikrama Reddy 1 Jan 3, 2022
A dashboard for managing Mineflayer bots, used for Hychat.

The dashboard uses Next.js and Chakra UI to create an interactive dashboard to manage Hypixel bot(s) and view chat logs. It also fetches messages from a back-end using an API (found in src/pages/api).

Hychat 2 Aug 2, 2022
Simple & Quick Access Addon For Homer Dashboard

Homer Dashboard - Firefox Addon Quick Access Homer Dashboard - Firefox Addon Usage Install Addon [ Firefox ] Configure The Addon Add The Quick Access

Varun Sridharan 7 Jan 22, 2022
A weather dashboard that features dynamically updated HTML and CSS using OpenWeather API data.

Weather Dashboard A weather dashboard that features dynamically updated HTML and CSS using OpenWeather API data. User Story AS A traveler I WANT to se

Benjamin Eidum 1 Apr 19, 2022
Weather-magic - Working with APIs to create a weather dashboard

Weather Magic link to website Following the link above will bring you to the Wea

null 1 Feb 3, 2022
An easy-to-use next.js administration dashboard implementation

An easy-to-use next.js administration dashboard implementation

IroncladDev 21 Oct 30, 2022
AMP: is a fast admin dashboard template based on FastAPI

AMP: is a fast admin dashboard template based on FastAPI Introduction AMP: is a fast admin dashboard template based on FastAPI. The project uses its o

Denis Bazarnov 17 Jan 1, 2023
Replacement for comma.ai backend and useradmin dashboard

Replacement for comma.ai backend and useradmin dashboard. Bundled with a modified version of comma's cabana to allow viewing & analyzing drives.

null 15 Jan 1, 2023