Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 437418

Summary:	Need to be able to limit bugzilla components used in the release Issues tab
Product:	Community	Reporter:	Greg Watson <g.watson>
Component:	Project Management & Portal	Assignee:	Portal Bugzilla Dummy Inbox <portal-inbox>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	wayne.beaton
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Mac OS X
Whiteboard:	stalebug

Description Greg Watson

2014-06-13 15:43:40 EDT

The "Issues" tab on the release page of the project web page seems to take it's content by looking for closed bugs that have a target milestone that corresponds to the release version.

However, some projects (e.g. PTP) have sub-probjects that use a different release version. Since the "Issues" tab just uses all bugzilla components, the list that is generated may contain the wrong information for these sub-projects.

Since there is not currently any way to link a sub-project to its corresponding bugzilla components, I think the best solution would be to allow the set of components used to generate the "Issues" tab to be customizable. That way the sub-project components could be removed. It would still be possible to see the "Issues" for the sub-project by viewing the sub-project release page.

Comment 1 Wayne Beaton

2014-06-13 22:47:34 EDT

This is a tough one. A design goal was to keep this simple.

If I understand correctly, you're using PTP product target milestones to mean different things for PTP and Photran. This just seems all-around confusing to me.

I also wrestle a bit with what it means to have a subproject participate in a release with the parent but with a different version.

Also, if Photran is participating with PTP in a release, there should only be one release record (owned by PTP). We don't generally expect there to be a release record for the subproject. I intend to include shared release records on the subproject pages at some point.

Finally, you can specify a component in the metadata.

Comment 2 Eclipse Genie

2016-06-08 17:48:56 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 3 Eclipse Genie

2018-06-02 18:24:30 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2020-05-23 13:48:53 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 5 Wayne Beaton

2021-09-30 11:17:06 EDT

The feature is problematic for multiple reasons. We're going to deprecate and remove it. There is some discussion on Bug 576364.