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
Project field within reported-issue versus Roadmap-menu (usi
Moderators: Developer, Contributor
Re: Project field within reported-issue versus Roadmap-menu
Not sure what you mean with it.Jaap wrote: Is there a way to toggle between Main- and Sub-projects within the Roadmap, so we will be able to Group or Segment them?
The roadmap shows the main and the sub-projects if you choose the main project in project selection drop down.
The roadmap shows the the sub-project if you choose a sub-project in project selection drop down.
Re: Project field within reported-issue versus Roadmap-menu
Let me try to describe by two public access-able examples of MantisBT using sites:
A) Have a look at the non-nested:
https://www.mantisbt.org/bugs/roadmap_page.php
Well when go to the Roadmap menu and check the projects-box, right side of screen, then you will see that there are no nested projects.
No issues here!
B) But when we visit:
http://doublecmd.sourceforge.net/mantis ... p_page.php
We see in the Roadmap
The Main-project : Double Commander
And the Sub-project: Tasks
Checking the project box we see:
Double Commander
>> Tasks
When opening issue the following issues 0000018 and 0001499 then is shown
ID 0001499
Project Double Commander
ID 0000018
Project Tasks
So the nested sub-project shows different Roadmaps, known:
MAIN Roadmap
SUB Roadmap
So I’m facing the same kind of issue like “Double commander“.
I would like to be able to have some kind of work-a-round by which I could toggle between them.
My intention is to add later on a Burn-down Chart to the Roadmap so I would expect:
1) The Main-project with all subproject issues included overview. (1 Chart)
2) The “Segmented overview” per Main/Subject project Road-map. (Chart for every segment)
** This second one is what now “actually shown”
** The first one is what I “also wanted”!
I hope that I described this quite complicated issue properly enough!
Remark:
I could filter perfectly with the Project-select box between “All Projects”, “Main-projects” and “Sub-projects” so filtering is not the issue. The issue is Main versus its sub-projects.
Selecting the main project shows me also its sub-projects but not in one listing.
Sincerely,
Jaap
A) Have a look at the non-nested:
https://www.mantisbt.org/bugs/roadmap_page.php
Well when go to the Roadmap menu and check the projects-box, right side of screen, then you will see that there are no nested projects.
No issues here!
B) But when we visit:
http://doublecmd.sourceforge.net/mantis ... p_page.php
We see in the Roadmap
The Main-project : Double Commander
And the Sub-project: Tasks
Checking the project box we see:
Double Commander
>> Tasks
When opening issue the following issues 0000018 and 0001499 then is shown
ID 0001499
Project Double Commander
ID 0000018
Project Tasks
So the nested sub-project shows different Roadmaps, known:
MAIN Roadmap
SUB Roadmap
So I’m facing the same kind of issue like “Double commander“.
I would like to be able to have some kind of work-a-round by which I could toggle between them.
My intention is to add later on a Burn-down Chart to the Roadmap so I would expect:
1) The Main-project with all subproject issues included overview. (1 Chart)
2) The “Segmented overview” per Main/Subject project Road-map. (Chart for every segment)
** This second one is what now “actually shown”
** The first one is what I “also wanted”!
I hope that I described this quite complicated issue properly enough!
Remark:
I could filter perfectly with the Project-select box between “All Projects”, “Main-projects” and “Sub-projects” so filtering is not the issue. The issue is Main versus its sub-projects.
Selecting the main project shows me also its sub-projects but not in one listing.
Sincerely,
Jaap
Re: Project field within reported-issue versus Roadmap-menu
You might want to add your thoughts to some known feature requests related to roadmap and sub-projects, e.g.
https://www.mantisbt.org/bugs/view.php?id=10368
https://www.mantisbt.org/bugs/view.php?id=10388
https://www.mantisbt.org/bugs/view.php?id=7865
...
https://www.mantisbt.org/bugs/view.php?id=10368
https://www.mantisbt.org/bugs/view.php?id=10388
https://www.mantisbt.org/bugs/view.php?id=7865
...
-
- Posts: 1
- Joined: 25 Oct 2016, 07:25
Re: Project field within reported-issue versus Roadmap-menu
I have been thinking of a similar functionality and happen to be working on the roadmap page this week. Willing to exchange information / examine together with you Jaap. You could pm me in dutch for clarity.