Website Link: https://bugtrackerproj-e0ecfff13106.herokuapp.com/
Hello, welcome to BugFree. This is a client based Bug Tracking Website where clients can submit tickets to an Institution's projects, providing the users of that Institution to have an organized view of the tickets associated with their projects based on varying ticket priority, type, and status
This website features 4 main roles: Admin, Project Manager, Developer, and Submitter
-
Admin:
- Have the ability to add/remove users from the Institution or from specific projects, create projects, changes roles of all users, assign developers to tickets, and edit information information for all tickets,
-
Project Manager:
- Have the ability to change the roles of user's within the projects that they are the managers of, add/remove users from those projects, assign developers to tickets, as well as edit ticket information associated with their project
-
Developer:
- Have the ability to update the priority and status of tickets they are assigned to
-
Submitter:
- Have the ability to create to create tickets for projects they are assigned to by an Admin or Project Manager
This is how the website looks upon loading, it has links for Home and Login
Upon Clicking the Home Link, you will see a small description of the Website in addition to a video tutorial to help new users navigate the site
On this page, a User can login if they already have an existing account. If a user is an administrator for an Institution, they can provide that Intitution's 'Admin Password' on login to be taken to their adminstator account. If a user who is not an admin gets a hold of the Admin Password, that user will get a error message and the admin of the Institution will be notified that their secure password has been leaked.
Here, users can register to join to an exisiting Institution
Finally, here users have the ability to register a new Instituion that other users can join as well
The user that is registering the new Institution will automatically be added to the list of Admin for that Institution. It is up to them to set up an 'Admin Password' for the Insittution, which is an additional password reserved only for admin of the Insittution. Users can can enter this additional password at the Login page in order to be taken to their adminstator acount.
After registering to join an Institution, a user will be presented with the following page, instructing them to wait until their request to join the Institution has been accepted by an administrator
This is what it looks like for the Admin when a user submits a join request to the Institution. The admin have the option to either accept or deny each request.
Once the Admin has accepted some join request, the 'Manage Users' section will show a table of all of the users, excluding other admin, in the Institution. As the admin, a user has the ability to edit the roles of other users, or remove others from the Institution entirely
When an Institution does not have any projects created yet, the 'View Projects' page will instruct you to create a new project to get started
Both the Project Manager and Admin have the ability to create new projects, where they can include a title, description, as well as a list of other users that they would like to include in the project
Once an Institution has some projects, the 'View Projects' section will be updated with additional information
- For Admin, this page will display all of the projects for the Institution
- For Project Managers, they will only be able to view projects that they have been assigned to
- This page is not available to view for Submitters and Developers
This section is available to both Admins and Project Managers
Admin and Project Managers have the ability to edit the roles of the users within the project, remove specific users, or add new users to this project
In this section, Admin and Project Managers can see all of the information associated with this project, such as assigned personnel as well as tickets
If there are no tickets for an Institution, this page will instruct users to wait until a Submitter has submitted new tickets
For a Submitter, this page will display all of the tickets that they have created, if there are none, they will be instructed to create a new ticket
When creating a ticket, a submitter can include the following information: title, description, type, priority (which can be either Low, Medium, or High), as well the project that they want this project to be associated with. Whenever a ticket is created, its default status is 'New', this can be changed by the Developer, which will be discussed later
After tickets have been created, the 'View Tickets' section will display additional informationn depending on the role of the user that is logged in:
- For admin, this section will display all of the tickets that are in this Institution
- For Project Managers, this section will display only the tickets that are associated with the projects that they are the managers of
- For Developers, this section will only show the tickets that they have been explicitly assigned to (More on this later)
Admins, Project Managers, and Developers have the ability to update tickets. Admins and Project Managers have the ability can update every aspect of a ticket, weheras developers can only update the status and priority of tickets. The Admin, Project Managers, and Developers all have the power to change the status of a ticket to one of the following: New, Open, In Progress, Resolved, and Additional Information Required
By default, when Tickets are created they do not have a devloper assigned to them, so it is up to either the Admin or the Project Manager to assign a deveoper to a given ticket
This is how updating a ticket looks for both the Admin and Project Manager:
This is how it looks on the developer side:
In the View Tickets section, users have the ability to view additional details of that ticket, such as when it was created as well as all of the history associated with that ticket. Additionally, in this section, users have the ability to leave comments on a ticket
Whenever a user leaves a comment on a ticket, both the developer and submitter of the ticket will be notified of the comment. Users can see that they have new notifications when the Notification logo turns white, as follows
Upon pressing it, a user can see all of their notifications as well as when the notification was sent
When the status of a Ticket turns to 'Additional Information Required', the Submitter of that ticket will get a ticket informing them to provide additional information on that ticket immediately
Then when that Submitter looks at the 'View Tickets' page again, they will see that their ticket will be labeled as 'Action Required', where they are required to change either the title or the description of the ticket, otherwise they will get an error
Once tickets have been created, the 'Dashboard Home' section will also be updated, and it will display different information based on the role of the user that is logged in
- Admin will see graphs breaking down all of the tickets in the Institution
- Project Managers and Developers will see a breakdown of the tickets associated with the projects they're on
- Submitters will see a breakdown of all of the tickets that they have created
- Developers will see a breakdown of the tickets that they are assigned to
