- Project Management
- Bug Management
| Stack | - | - | - | - | - |
|---|---|---|---|---|---|
| FrontEnd |
|
|
|
|
|
| BackEnd | |
|
|
|
|
Since the core application is protected through authentication, the first page you will be directed to will be the register page.
Once you have registered, a backend service will check if you are an authorised user or not. Upon succesful authentication, you will be then directed to login page.
...
If the user is logged in as a Project Manager, he/she will have the option to create new project and assign a team to it and view the bugs reported for each project.
Upon clicking on the project name, the project manager will be redirected to a new page, on which he/she can view the project details. The project details that are displayed are: - Project ID: Every project is assigned a unique ID. - Project Name - Description: A description of the project. - Start Date: The start date of the project. - Status: In Progress/Completed.
If the user is logged in as a Developer, he/she will have the view to the assigned projects and the bugs reported for each project. The developer can mark a bug for closing.
If the user is logged in as a Tester, he/she will have the view to the assigned projects and the option to report new bug to project.
Upon clicking on the report bug button, the tester will be redirected to a form which needs to be filled for reporting the bug. The form includes the following fields:
- Bug ID: Every bug is to be assigned a unique ID.
- Title
- Description: A description of the bug.
- Project ID: The id of the project for which the bug is reported.
- Created By: The id of the tester reporting the bug.
- Open Date: The date on which bug was reported.
- Assigned By: The id of the PM assigning the bug.
- Closed By: The id of the developer closing the bug.
- Closed On: The date on which bug was closed.
- Status: Open/Closed.
- Severity Level: Critical/Major/Minor/Trivial.