Skip to main content

Hi there, 

From time to time, I find myself working on branches that remain open for extended periods. To better manage these situations, I would like to track all changes made to a branch since its creation.

Is there a way to generate a timeline or log of these changes?

Such a feature would greatly support maintaining a structured development history, particularly as we follow a standardized documentation template. Comprehensive documentation often gets overlooked due to time constraints, so having an automated or semi-automated way to track changes would help bridge that gap.

This functionality could also enhance team communication by providing a clear reference point, reducing the likelihood of misunderstandings. Additionally, it would make it easier to identify unintended modifications, such as those introduced through accidental interactions, before they escalate into issues in production.

Kind regards,

Balazs Szeder

Hi Balazs,

Currently the Software Factory offers a couple ways of seeing differences between branches, such as the Origin and your Feature branch.

To see the differences between them, you can make use of the Difference analysis, available in the Software Factory at Models > Difference analysis. With this you can see which objects are only present in the Origin, or only present in your branch, or object data that is different between the two.

Other way if by creating a merge session and inpecting the Merge impact. Here you see all actions that will have an effect if you would choose to execute the merge session. This is my preferred way at the moment. With this you are also able to exclude certain actions if, for instance, it was a temporary change.

With the implementation of this idea, I will be looking into a Merge impact that will be shown like a "Journey of changes”. All the impact will be sorted based on when it (last) happened. In addition to that, I will also be looking into a Change log kind of overview where you can see what a merge session has added. The merge session description will play a huge role in this.

Does this answer your questions?

Terms & ConditionsCookie settingsAccessibility statement