Project page bug list doesn't exist any more

Summary

On an Eclipse project page there used to be a list of bugs fixed by a release. For example: https://www.eclipse.org/mat/1.13.0/noteworthy.html linked to https://projects.eclipse.org/projects/tools.mat/releases/1.13.0/bugs

We used add to the noteworthy page all the bugs listed in our release, but somewhere I saw a recommendation to add a link to the bugs on the project page instead.

Steps to reproduce

Go to https://projects.eclipse.org/projects/tools.mat/releases/1.13.0/bugs

What is the current bug behavior?

The page just looks like the overview page https://projects.eclipse.org/projects/tools.mat/releases/1.13.0

What is the expected correct behavior?

A list of bugs on the project page.

Relevant logs and/or screenshots

Priority

• Urgent
• High
• Medium
• Low

Severity

• Blocker
• Major
• Normal
• Low

Impact

The new and noteworthy page doesn't have a link to display the bugs. A work-around might be to modify the project page with a link to the fixed bugs. https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=RESOLVED&bug_status=VERIFIED&bug_status=CLOSED&resolution=FIXED&classification=Tools&product=MAT&target_milestone=1.13.0 or to create a theme, as below.

Comments

Perhaps this is related to projects moving off Bugzilla, and perhaps the old page just worked with Bugzilla. I do see there is a way to add links to bugs on the themes section of the release plan pages, which I have used for 1.14.0: https://projects.eclipse.org/projects/tools.mat/releases/1.14.0/plan

Is my understanding correct? What are the current recommendations to show fixed bugs for a release? https://www.eclipse.org/projects/handbook/#resources-issues

Eclipse projects must use an Eclipse Foundation-provided issue tracker. Project teams may opt to use either the Eclipse Bugzilla instance or — for projects that use GitHub — GitHub Issues instances associated with Eclipse Foundation-managed GitHub project repositories.

and I presume gitlab.eclipse.org is also acceptable.

@wbeaton any insights at how this used to work?

Thanks.

moved from eclipsefdn/helpdesk#2625 (moved)

The feature was retired. See #83 (closed)

Current advice is to maintain a change log in the project repository.

The Eclipse GitLab instance is not only acceptable, using it as a Bugzilla replacement is recommended.

Is there anything to be done by the webdev team for this?

I will close this issue. But please reopen if you think the webdev team needs to take any action on this.

Thanks.

closed