Building an Issue Management System frontend

Before we begin building the Angular frontend app, let's go over the goal of the project once again.

The system will facilitate a user to access the list of issues and view its details. A user should also be able to create and update the issue. It would also be helpful to get updates about various issues in the system. The activities done for an issue can be tracked by means of comments added to it. It would also be nice to be able to chat with other users.

Part of the goal was addressed when we built the backend microservices. The services, when put together, provided the needed business logic and persistence of the domain model. Here's a logical view of a component-based angular app connected to the backend IMS microservices:

IMS angular app logical view with microservices

It is possible and often desirable to have the app development done independently from the actual microservices. The server-side team could have their own release cycles that...