Fork and merge: Milestone explorer - handle document addition/deletion - UI
SUMMARY
When working on a clone proposal, the users are free to modify all the cloned documents, and these changes are tracked in track changes, but they are also allowed to ADD/REMOVE documents such as Annexes of LFS. In this case, when the cloned is consolidated, there needs to be a way for the receiving end (Lead DG) to consult such document level changes and act upon them.
In Legacy Vaadin version of LEOS, this functionality was covered according to the following documentation : https://citnet.tech.ec.europa.eu/CITnet/confluence/pages/viewpage.action?pageId=1148028673
ACCEPTANCE CRITERIAS / GOALS
Implement support for all UI changes the are present in legacy Vaadin application:
- Add the "i" on proposal viewer informing that the cloned proposal contains document changes do be handled. NOTE: Be sure to include the tooltip present in the image above
- Add all visual changes indicated in image above for milestone explorer when viewing the contribution
NOTE: The backend support for the actions Accept/Reject themselves are not in the scope of the current ticket, only the UI components, i.e., add the bottons on the screen. This shall be done on a separate ticket.