Ticket #362 (Clôturé Amélioration: Résolu)
Clone delayed items
| Reported by: | gbastien | Owned by: | gbastien |
|---|---|---|---|
| Priority: | Haute | Milestone: | PloneMeeting 1.8 |
| Component: | Produit PloneMeeting | Severity: | Non bloquant |
| Keywords: | Cc: |
Description (last modified by gdelannay) (diff)
When an item is delayed, we should clone it: (a) either manually (an additional button allows to trigger the cloning), (b) either automatically when a specific transition is triggered on the meeting.
Behaviour (a) and (b) should be selectable and configurable from the meeting config.
The cloned item is put back in "created" state.
Change History
comment:1 Changed 2 years ago by gbastien
- Owner set to gbastien
- Status changed from Nouveau to Assigné
comment:2 Changed 2 years ago by gbastien
La "clonage" du point ne se fera plus lors de la clôture du Meeting (car celui ci intervient bien souvent plusieurs semaines après la fin de la séance) mais lors du report du point.
- dans doDelay cloner le MeetingItem?
- garder un lien entre les 2 items (le reporté et le nouveau)
--> garder le lien sous forme de String Persistent sur la classe MeetingItem? dans lequel on sauvegarde un uid...
- à faire sur PloneMeeting? ou sur MeetingCommunes?? A priori dans PloneMeeting? s'il s'agit d'un besoin global...
comment:3 Changed 2 years ago by gbastien
- Component changed from Product MeetingCommunes to Product PloneMeeting
- Milestone set to PloneMeeting 1.6
comment:4 Changed 2 years ago by gdelannay
- Description modified (diff)
- Summary changed from Gestion des points reportés to Clone delayed items
comment:5 Changed 14 months ago by gdelannay
- Milestone changed from PloneMeeting 1.6 to PloneMeeting unplanned
comment:6 Changed 7 months ago by gdelannay
- Status changed from Assigné to Clôturé
- Resolution set to Résolu
- Milestone changed from PloneMeeting unplanned to PloneMeeting 1.8
Done. A reference field "predecessor" allows to store, on an item, its predecessor that has been delayed in a previous meeting. The item is cloned when transition "delay" is triggered.
Note that, for the moment, the predecessor fields does not go through webdav.
