Project field within reported-issue versus Roadmap-menu (usi
Posted: 30 Aug 2016, 14:36
Project field within reported-issue versus Roadmap-menu (using Main- and Sub-projects).
Following case:
1. We define within a Main-project several Sub-projects.
2. We define by “Manage Projects” for the Main-project a (release)- version, this with the options release untagged. The Sub-project is inheriting this setting.
3. We select a reported issue and add to this issue the target-version and saving this.
4. Within the Roadmap-menu the ticket will be shown in the section:
- Main-project OR
- Sub-project.
This depends on what was defined into the “Project”-field of the reported issue/ticket.
Question:
Is there a way to toggle between Main- and Sub-projects within the Roadmap, so we will be able to Group or Segment them?
- For a complete overview then I would choose the Main-projects.
- For a segmented overview the Sub-projects.
This without the intention to change the ticket/issue its project value!
Sincerely,
Jaap
Following case:
1. We define within a Main-project several Sub-projects.
2. We define by “Manage Projects” for the Main-project a (release)- version, this with the options release untagged. The Sub-project is inheriting this setting.
3. We select a reported issue and add to this issue the target-version and saving this.
4. Within the Roadmap-menu the ticket will be shown in the section:
- Main-project OR
- Sub-project.
This depends on what was defined into the “Project”-field of the reported issue/ticket.
Question:
Is there a way to toggle between Main- and Sub-projects within the Roadmap, so we will be able to Group or Segment them?
- For a complete overview then I would choose the Main-projects.
- For a segmented overview the Sub-projects.
This without the intention to change the ticket/issue its project value!
Sincerely,
Jaap