Implementing changes
Requirements change continuously, so a requirement that was implemented earlier may need its new version (the new requirement text) to be implemented. The carrier of these changes is also the Enhancement. You can say that an Enhancement is a version of a requirement that has the properties of estimation, planning, and decomposition by type of work. In general, Enhancements are linked to
requirements by a "many-to-many" relationship.
When implementation of an Enhancement is finished, its text (description) can be frozen so that later changes to the linked requirement do not change the assignment that has actually already been implemented. This behavior is achieved by the system action "Freeze the text of included artifacts in the description", which can be attached to the final state of the Enhancement.
After changes are made to the requirement text and a new Enhancement is created, the system shows the text of the changed requirement in "delta" mode. This lets you quickly find the changes in the assignment that appeared in the new version of the requirement. In this way, developers, testers, technical writers, and other Participants of the technical team do not need to compare requirement versions every time; the assignment text already shows all of this:
