• New plugin Folder
• plugin provides "_in_folder" artifact link type
  • Usable for XML import
• plugin provides "Folder" tab in artifact (shown when there at least on "_in_folder" link type)
• The tab shows a roll-up view of "_in_folder" (see below)
• At this step, it's not possible to manipulate Folder from the UI
• Project can now have a tracker of type "Folder". In project only a tracker can have this type. The tracker can be flagged as a folder type only by XML import, no UI flag will be displayed
• An artifact can't be in more than one folder. At xml import, if we found more than 1 _in_folder link, the first artifact is added with correct nature, next artifacts will have an empty nature and an error is displayed

View:

Given

(`-- stands for _is_child)

Story A
`-- Task T1
    |-- Task T1.1
    `-- Task T1.2
Story B
`-- Task T2
---------------------
Folder F1
|-- Subf F1.1
`-- Subf F1.2

And

Story A   -_in_folder-> Folder F1
Task T1   -_in_folder-> Folder F1
Task T1.1 -_in_folder-> Subf F1.1
Task T1.2 -_in_folder-> Folder F1
Story B   -_in_folder-> Folder F1
Task T2   -_in_folder-> Subf F1.2

Then resulting view:

Id                 | Title | Status | ... | Parent
--------------------------------------------------
Story A            |       |        |     | Folder F1
Story B            |       |        |     | Folder F1

And if I expand everything:

Id                 | Title | Status | ... | Parent
--------------------------------------------------
Story A            |       |        |     | Folder F1
`-- Task T1        |       |        |     | Folder F1
    |-- Task T1.1  |       |        |     | Folder F1 / Subf F1.1
    `-- Task T1.2  |       |        |     | Folder F1
Story B            |       |        |     | Folder F1
`-- Task T2        |       |        |     | Folder F1 / Subf F1.2

Fields to display:

• Same as Artifact links v2 (Id, project, tracker...)
• + "Folder"

Ways of working

• The inital load of "Folder" tab loads all "in_folder" links directly connected to the artifact
  • In the example above (Story A, Task T1, Story B and Task T2)
  • Artifacts are show relative to their parents (T1 is shown as a child of Story A)
  • Display is collapsed by default
  • Initial load only deal with first level "in_folder" (we don't inspect Folders's children)
• Elements with the same parent are displayed according to their ranks
• Data contraints
  • There is none, people can des-organize folders the way they want.