how to keep the description in the changes

0

HI,
There is probably no great solution to this.
For example, I try to add all reports in the documentation section, whether on attributes, shares, etc.
Of course, not all, only those that are important in the context of changes.
This is very helpful when searching.
But you also need to remember about it and add it, and use a reporting system that will generate numbers for us under which we can then search.

Regards.

Hi,

Tracking changes is a challenge in all software development related projects.
In the latest versions of Webcon you could use the user voice feature, but it won't solve everything.

I'm currently using GitLab for that task.
Each introduced change -> New issue
Each package -> Milestone

Issues are changes, milestones group them in packages which are released.
Basically there is no new package created without a milestone.
After each release I'm creating markdown write up about functional changes, bug fixes etc. based on the closed milestone.
That write up is inserted inside description of the package.

I'm also using git for storing all the packages in one place, but if you don't need that part, then any project management might be a good choice.
Jira, Asana, Trello, Planner in teams - depends on your needs.

It requires scrupulousness to create issues for each change, even those quick fixes on prod, and applying them to all environments but in the end I'm feeling safe when deploying.