Systems and methods for tracking features in a development environment

1. A system for tracking features of one or more applications in a software development environment, the system including a non-transitory computer- readable medium storing computer-executable instructions thereon such that when the instructions are executed, the system is configured to:

monitor the one or more applications, generating records associated with the one or more applications and tracking progress data associated with features of the one or more applications;

determine, from a scope of interest data, a set of applications from the one or more applications, the set of applications being associated with a user;

determine, from the scope of interest data, roles for each application in the set of applications, wherein the roles are described in relation to the user;

extract, from log data, user log data associated with the set of applications based on the roles for each application in the set of applications;

extract, from the progress data, user progress data associated with the set of applications based on the roles for each application in the set of applications; and

provide, to a client device via an application programming interface (API), the user progress data associated with the set of applications and the user log data associated with the set of applications for displaying on the client device.

2. The system of claim 1 , wherein the scope of interest data includes a tree structure with a parent node identifying the user and one or more leaf nodes identifying the set of applications.

3. The system of claim 2 , wherein the tree structure includes intermediate nodes that identify other users.

4. The system of claim 3 , wherein the user progress data are extracted based on the intermediate nodes and wherein the user log data are extracted based on the intermediate nodes.

5. The system of claim 3 , wherein one of the intermediate nodes is a pointer to a first scope of interest data associated with a first user, the first scope of interest data stored separately from the scope of interest data.

6. The system of claim 1 , wherein the roles are selected from the group consisting of: ownership, contributor, and follower.

7. The system of claim 1 , when the instructions are executed, the system is further configured to:

receiving one or more scope instructions from the client device; and

populate the scope of interest data based on the one or more scope instructions.

8. The system of claim 7 , wherein the one or more scope instructions include:

an instruction to add a first user to the scope of interest data, the first user being related to the user in an ownership relationship;

an instruction to remove a second user from the scope of interest data;

an instruction to add a first application to the scope of interest data, the first application being an application in the set of applications, and the first application being related to the user in an ownership relationship;

an instruction to add a second application to the scope of interest data, the second application being an application in the set of applications, and the second application being related to the user in a following relationship;

an instruction to add a third application to the scope of interest data, the third application being an application in the set of applications, and the third application being related to the user in a contributing relationship;

an instruction to remove a fourth application from the scope of interest data; or any combination thereof.

9. The system of claim 1 , wherein the records are generated according to a publisher/subscriber model.

10. The system of claim 9 , further configured to:

subscribe to a Kafka topic, wherein generating the records includes generating records associated with the Kafka topic.

11. A method for tracking features of one or more applications in a software development environment, the method including:

monitoring the one or more applications to generate records associated with the one or

more applications and progress data associated with features of the one or more applications;

determining, from a scope of interest data, a set of applications from the one or more applications, the set of applications being associated with a user;

determining, from the scope of interest data, roles for each application in the set of applications, wherein the roles are described in relation to the user;

extracting, from log data, user log data associated with the set of applications based on the roles for each application in the set of applications;

extracting, from the progress data, user progress data associated with the set of applications based on the roles for each application in the set of applications; and

providing, to a client device via an application programming interface (API), the user progress data associated with the set of applications and the user log data associated with the set of applications for displaying on the client device.