Welcome to the Bug-Report!
You have been tasked with creating a tool to better report bugs for your team. The goal being, to better track bugs in your application, as well as the process taken to solve them.
All bugs will have a title, description, who reported the bug, closedDate and whether or not it has been closed.
Users can also add notes to the bug report providing detailed steps towards the bugs resolution.
Once a bug has been closed, no further editing is allowed.
Here are some mock-ups from the client.
From the Home page users can view all the bugs that have been added, color coded to which are open and closed(by status). You should be able to filter the bugs based on their status(open or closed).
Try to implement pagination here(display limited number of bugs per page). Modals for creating bugs instead of a static form could be a nice feature as well.
The details view provides some additional information about the bug, as well as showing all the notes made by other users. Here notes can be created or removed.
See if you can implement the ability to go next or previous from this page. Modals for creating notes would be a nice feature instead of a static form always visible on the page.
var bug = new Schema({
closed: { type: Boolean, required: true, default: false },
description: { type: String, required: true },
title: { type: String, required: true },
reportedBy: { type: String, required: true }, //The provided name for who reported the bug
closedDate: { type: Date}
}, { timestamps: true, toJSON: { virtuals: true } })var note = new Schema({
content: { type: String, required: true },
bug: { type: ObjectId, ref: 'Bug', required: true },
reportedBy: { type: String, required: true }, //The provided name for who made the note
flagged: { type: String, enum: ["pending", "completed", "rejected"] }
}, { timestamps: true, toJSON: { virtuals: true } })baseUrl:
'https://localhost:3000/api'
Get
/bugs: returns a list of all the bugs
/bugs/:id: returns a single bug with all it's data
/bugs/:id/notes: returns all notes for a given bug id
Post
/bugs: Creates a new bug
/notes: Adds a new note to the bug.
Put
both of these can only be done if bug is open
/bugs/:id: Edits bug
/bugs/:id/notes/:id: Edits note. (not required)
Delete
There is no true bug delete, only changing the status of a bug to closed.
/bugs/:id: Changes status of bug from open to close
/bugs/:id/notes/:id: Deletes note.
- At least 2 supported front end routes
- Home shows all bugs
- BugDetails displays the details of a bug and its Notes
- Bugs can be filtered by their status
- Creating a new bug automatically navigates to the BugDetails view
- Navbar to allow navigating back to Home view
- Styling Indication on main page that bug is closed (color, strike-through, etc.)
- Bugs display last modified date
- Bugs can be created from the Home view
- Bugs can be closed from the BugDetails view
- User is prompted "are you sure?" when closing a Bug
- Notes can be added and removed from a bug in the BugDetails view
- User prompt to remove Note from Bug
- A Bug can be edited
- Cannot edit a Bug after it is closed
- Implement user auth
- Modals for creating Bugs
- Modals for creating Notes
- Use sweet alert for prompts
go to http://localhost:3000/#/test-runner to use a testing suite for your server.