System and Method for Bidirectional Replication of Scope Changes for Work Items Between Applications

1. A method for bidirectional replication of scope changes for work items between applications, the method comprising steps of: a. identifying and fetching a scope change from a scope change event for a work item in a source application; b. transforming the scope change of the work item from the source application to a target application, and wherein an old-source-object in the source application is transformed to obtain an old-target-object and a new-source-object is transformed to obtain a current-target-object of the work item while transforming the scope change of the work item from the source application to the target application; c. checking for conflicts between the old-source-object of the source application and the current-target-object of the target application, and resolving the conflicts if any as per user configuration; d. validating whether the work item is in an expected state on the target application; e. moving the work item from one scope to another scope in the target application; and wherein, then the method the work item in an old scope of the target application deprecated and a new work item in the target application in a new scope created, when the target application fails to support the moving of the work item from one scope to another scope; and f. performing update operations depending upon the properties updated in the source application, and the work item is transitioned from the old scope to the new scope of the target application.

2. The method according to claim 1, wherein the scope change includes a change of the work item or movement of work item, and wherein the scope change event comprises the old-source-Object and the new-source-object, and wherein the old-source-object comprises values set in the work item before the scope change, and wherein the new-source-object comprises values set in the work item after the scope change.

3. The method according to claim 1, wherein the step of fetching the scope change event for the work item of the source application comprises the steps of: a. detecting and fetching the scope change events for the work item within a given scope from the source application; and wherein the scope change events comprise an object unique identifier on which an event occurred, time of an event, changes made to the work item, old values comprising properties of the work item before the scope change and new values comprising the properties of the work item after the scope change; b. iterating through the scope change events to identify the objects that are moved to the scope from other scopes; and c. synchronizing all the scope changes of the objects with the target application.

4. The method according to claim 1, wherein the step of transforming the old-source-object in the source application comprises the steps of: a. obtaining the old scope from the scope change events; b. obtaining the work items object properties comprising old values from the scope change events; c. fetching user configuration for transformation of the old scope of the work item; d. transforming the old values to obtain transformed-old properties; and e. returning transformed-old properties.

5. The method according to claim 1, wherein the step of transforming the new-source-object comprises the steps of: a. obtaining the new scope from the scope change events; b. obtaining the work items object properties comprising new values from the scope change events; c. fetching user configuration for transformation of the new scope of the work item; d. transforming the new values to obtain transformed-new properties; and wherein the transformed-new properties comprises those settings the user needs to perform in case the target application fails to support moving objects between the scope; and e. returning the transformed-new properties.

6. The method according to claim 1, wherein the transformation of the scope change of the work item from the source application to the target application depends on the user configuration and the transformation information configured by the user for the old scope of the work item and the new scope of the work item.

7. The method according to claim 6, wherein the user configuration comprises properties of the source application intended to be synchronized to the target application by the user while creating the object and updating the object.

8. The method according to claim 1, wherein the step of managing the conflicts between the old-source-object of the source application and the current-target-object of the target application, comprises the steps of: a. obtaining the current object properties of the work item from the target application; b. comparing the transformed-old properties of the work item with the current-target-object; c. comparing the scope changes between the transformed-old properties and the current object properties of the target application; d. resolving the conflict, if there is any difference in the scope changes using user's conflict resolution settings.

9. The method according to claim 1, further comprises fetching the user configuration by deprecating the work item in the target application including soft deleting or updating the work item object by adding notes or comments, for deprecating the work item in the old scope of the target application.

10. The method according to claim 1, wherein the step of moving the work item from one scope to another scope in the target application if the target application fails to support the movement of the work item, comprises the steps of: a. fetching the existing work item object in the target application; b. constructing new work item object in the new scope of the target application by: i. setting object properties in the new work item object; ii. creating the new work item object in the target application; iii. copying comments, attached files, links and any other field from the existing work item object to the new work item object; c. fetching the user configuration for marking the work item objects to be deprecated in the target application; d. applying the user configuration for the deprecated work item objects to the existing work item object; and e. updating a persistent data store to not integrate any updates with deprecated work item objects.

11. A system for bidirectional replication of scope changes for work items between applications, the system comprising: a. a scope change identification module configured to identify and fetch a scope change from a scope change event for a work item in a source application; b. a transformation module configured to transform the scope change of the work item from the source application to a target application; wherein the transformation module is configured to transform an old-source-object in the source application to obtain an old-target-object and to transform a new-source-object to obtain a current-target-object of the work item while transforming the scope change of the work item from the source application to the target application; c. a conflict management module configured to check for conflicts between the old-source-object of the source application and the current-target-object of the target application, and resolving the conflicts if any as per user configuration; d. a validation module configured to validate if the work item is in an expected state on the target application; e. a synchronization module configured to move the work item from one scope to another scope in the target application, and wherein the synchronization module is configured to deprecate the work item in an old scope of the target application and create a new work item in the target application in a new scope when the target application fails to support the movement of the work item from one scope to another scope, then; and f. a scope updation module configured to perform update operations depending upon the properties updated in the source application, and the work item is then transitioned from the old scope to the new scope of the target application.

12. The system according to claim 11, wherein the scope change identification module is configured to scope change by performing a change of the work item or movement of work item, and wherein the scope change event comprises the old-source-Object and the new-source-object, and wherein the old-source-object comprises values set in the work item before the scope change, and wherein the new-source-object comprises values set in the work item after the scope change.

13. The system according to claim 11, wherein the scope change identification module is configured for fetching the scope change event for the work item of the source application by: a. detecting and fetching the scope change events for the work item within a given scope from the source application, and wherein the scope change events comprise an object unique identifier on which an event occurred, time of an event, changes made to the work item, old values comprising properties of the work item before the scope change and new values comprising the properties of the work item after the scope change; b. iterating through the scope change events to identify the objects that are moved to the scope from other scopes; and c. synchronizing all the scope changes of the objects with the target application.

14. The system according to claim 11, wherein the transformation module is configured for transforming the old-source-by: a. obtaining the old scope from the scope change events; b. obtaining the work items object properties comprising old values from the scope change events; c. fetching user configuration for transformation of the old scope of the work item; d. transforming the old values to obtain transformed-old properties; and e. returning transformed-old properties.

15. The system according to claim 11, wherein the transformation module is configured for transforming the new-source-object by a. obtaining the new scope from the scope change events; b. obtaining the work items object properties comprising new values from the scope change events; c. fetching user configuration for transformation of the new scope of the work item; d. transforming the new values to obtain transformed-new properties, and wherein the transformed-new properties comprises those settings the user needs to perform in case the target application fails to support moving objects between the scope; and e. returning the transformed-new properties.

16. The system according to claim 11, wherein the transformation module is configured to transform the scope change of the work item based on the user configuration and the transformation information configured by the user for the old scope of the work item and the new scope of the work item.

17. The system according to claim 16, wherein the user configuration comprises the properties of the source application intended to be synchronized to the target application the user while creating the object and updating the object.

18. The system according to claim 11, wherein the conflict management module is configured for managing the conflicts by: a. obtaining the current object properties of the work item from the target application; b. comparing the transformed-old properties of the work item with the current-target-object in the target application; c. comparing the scope changes between the transformed-old properties and the current object properties of the target application; and d. resolving the conflict, if there is any difference in the scope changes using user's conflict resolution settings.

19. The system according to claim 11, wherein the synchronization module is configured to fetch the user configuration for deprecating the work item in the old scope of the target application by deprecating the work item in the target application including soft deleting or updating the work item object by adding notes or comments.

20. The system according to claim 11, wherein the synchronization module is configured for moving the work item from one scope to another scope in the target application when the target application fails to support the movement of the work item, by: a. fetching the existing work item object in the target application; b. constructing new work item object in the new scope of the target application by: i. setting object properties in the new work item object; ii. creating the new work item object in the target application; iii. copying comments attached files, links and any other field from the existing work item object to the new work item object; c. fetching the user configuration for marking the work item objects to be deprecated in the target application; d. applying the user configuration for the deprecated work item objects to the existing work item object; and e. updating a persistent data store to not integrate any updates with deprecated work item objects.