When you use Client GUI to upload SCM files into a review, you get the source (SCM) file structure uploaded to a review’s Review Materials section.
However, when you use the Web UI to upload files (that are NOT in CM) to a review, you are limited to a ‘flat’ file system, where ALL your files are at the top level. You can’t upload folders (or nested folders), and the Web UI doesn’t allow you to ‘create’ a folder to upload files into. Drag-and-drop will also not recognize folders dragged into a review.
We have several instances where this would be useful
- a) General nesting, where a folder structure will match the known development structure. As in:
Project
> Guidance
>> Algorithms.c
>> exec.c
> Nav
>> compensation.c
>> calc_V.c
>Include
>>comm.h
>>instruments.h
Documentation
>requirements.docx
>design.docx
- b) Test results, where we have several copies of the same file name, yet each is unique to where it lives. As in:
Test1
> input.txt
>results.txt
>script.tcl
Test2
> input.txt
>results.txt
>script.tcl