nciganovic / BugTrackerApi

.NET Core Web API for bug tracker

BugTrackerApi

.NET Core Web API for bug tracker

Documentation

Introduction

BugTrackerApi is api for tracking bugs. It is supposed to be used by the IT companies to keep track of the current tasks and projects.

• If user is unauthorized his only available action is to login or register.
• If user is authorized he can have different roles and based on theese roles he can preform certain actions.

Database schema

Controllers

I will now explain what are controllers supposed to do so you can get a clear picture of the capabilities of this project.

Account

• Unauthorized users can preform login and register operations. If user registers successfully, he will be notified via email.
• During registration password taken from user will be hased and and only hash and salt will be stored in database. Code for this is available at BugTracker/Application/Hash
• If login credentials are valid user will recive his JWT token
• If user is authorized he can change his inforamtions at /api/account/changeProfile

ApplicationUser

• ApplicationUser table is table that is representing users of application.
• Controller contains methods for CRUD operations.

Attachment

• Is a pdf file or image that is used to better describe goal of the task.
• Controller contains methods for CRUD operations.
• Files are stored in wwwroot/images

Comment

• Ability to write comment for specific task.
• Users can have dicussion.
• Controller contains methods for CRUD operations.

ProjectApplicationUser

• Showing users that are working on specific project
• Showing projects that specific user works on
• Add user to project or vice versa

Project

• Project that developers are working on
• Controller contains methods for CRUD operations.

RoleCase

• Connecting role ids to use case ids
• This enables that only user with specific role can do certain actions.

Role

• Role that is attached to specific user which grants his specific actions

Ticket

• Most imporant table in this project
• Users can create tickets for other users
• There are two types of updates, fake and real
• With fake new instance will be created with reference on old one, this is done so users can see history of specific task
• With real update, update will work as normal and new instance will not be created.

UseCaseLog

• When every action is executed, information will be stored in this table.
• There is ability to fully search through use case logs.