Hi,
If you introduced a custom ticket field 'project', the plugin just allows you to:
- assign your milestones to 1 project
- assign your versions to 1 project
- assign your components to n projects
You're not required to assign.
After assignment the advantage is you can filter the timeline and roadmap by projects (multi-selection box), means you'll see only desired milestones and also versions on /roadmap, and you'll see only desired tickets (labeled with the project name) on /timeline. That's the actual feature which SimpleMultiProjectPlugin brings to you.
You can still create tickets without assigned project, milestone or version or a combination of them, the plugin does not care, but you probably won't see them on /roadmap then. I also have that use case here that tickets belong to a (bugfix release) version but not to a milestone because both are different things here and the last milestone of that project can date back some time already. It's up to you to populate the tickets with useful information, but actually just for you that you later can easily find them by checking the lists behind the progress bars of milestones and versions on /roadmap or in your ticket queries.
CU, F@lk
----
R&D Software
Baumer Optronic GmbH
www.baumer.com
Gesch?ftsf?hrer: Dr. Albert Schmidt* Dr. Oliver Vietze
Sitz der Gesellschaft: Radeberg
Amtsgericht Dresden: HRB 15379
Ust. ID: DE 189714583