Tuleap 16 est là ! Assistez à l'événement virtuel le 17 octobre à 10h30. Inscrivez-vous ici !

  •  
     
    story #12634 Add custom metadata in modal
Summary
Empty
Add custom metadata in modal
Empty
Custom metadata can be:
- string/text/list/date (like existing)

Custom Metadata are inherited from parent folder.
=> if a parent has a custom metadata defined, it will be displayed as defaut input value in modal

Metadata can be applied for folder
=> they shoudl be inehrited from parent

If item is a folder there is an option to apply recursively the metadata

If metadata are not required the > More option is collapsed
If at least one metadata is required, the required metadata are visible, the optionnal metadata are still hidden by default
(to be checked with design)

Technically:
- POST/PUT docman_items existing routes should be updated and should enable the saving of new metadata
- GET docman_items should return the required
+ possible other values for list
+ type of metadata field
Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#12634
Marie Ange Garnier (marieange)
2019-08-21 12:26
2018-12-20 10:30
4021

References
Referencing story #12634

Git commit

tuleap/tuleap/stable

Add new route project/id/docman_metadata 68c9c1d752
metadata key should not be provided at document creation 506b9f2050
update POST embedded/link/wiki/folder/empty 3be9419754
POST files store metadata bcaf275885
Custom metadata are taken in account in create new document modal 99f09a46c1
Extract part of updateFromRow in dedicated objects fe2d333d01
String metadata are inherited from parent in new item creation 108a1bf274
Fix "is_required" key value of the Metdadata RESTs representations 7b9084bb7d
List metadata without multiple values are inherited from parent in new item creation 6535a6bdb3
Add missing is_requied property for list tests f6a4e20b12
Multiple list value metadata are inherited from parent in new item creation b6de7d58a4
PUT metadata files/embedded/wiki/link/empty 38dfde25f0
We should not be able to update root title by UI b38e8bf873
Date metadata are inherited from parent in new item creation 634a83782c
Enforce metadata key usage in backend 6723bf8e12
New folder should have same behaviour than item creation a1af13947d
Backend should not permit user to submit required metadata without any values 81f522902f
Refactoring: have a better naming for metadata representations e886b552bc
Choose metadata at folder/document creation bae6300df8
PUT folder metadata 0cb4675261
Update custom metadata with the update properties modal 1533af11a4
Permissions and metadata updates are not propagated to the sub-items of the current folder edcdfaccba
Update properties modal should always have its footer visible f7e39335a4
Take design feedback in account 75ca861455
Add the recursion options for custom metadata at folder update 322193cd73
Check / uncheck all the custom metadata according to the recursion option at folder update 66d13897e1
fix the error at folder creation when a metadata is a list e20bb7cb5b
Custom properties should be displayed for new folder when status property is not enabled for project f294bc0895
List with multiple values update does not work 7fbfe656d0

Follow-ups

User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes