Bugs fixed only in development release do not show up in default searches

Bug #1594640 reported by Jeremy Bícha
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
New
Undecided
Unassigned

Bug Description

I triaged bug 1269154 about the Apache example config in WordPress needing to be updated.
I marked the bug fixed since it was fixed in Ubuntu 15.04 but I marked it Triaged for trusty (Ubuntu 14.04 LTS).

Now the bug doesn't show up when someone visits

https://bugs.launchpad.net/ubuntu/+source/wordpress

You can see this effect even when not logged in with a clean browser profile (it's not that I've set my Launchpad personal settings wrong.)

This makes it more difficult for users of supported releases to tell if a bug that affects them has already been reported since by default they can't see bugs that have known fixes but that haven't yet been SRU'd back to the Ubuntu release they they are using.

What should happen
==================
Bugs marked Fixed in one release but still open in other supported releases should show by default in bug lists and seaches.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.