Build farm and build machines have their own unusable tabs
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
Low
|
William Grant |
Bug Description
The location bar on <https:/
The same problem occurs on the page for an individual build machine, e.g. <https:/
This can be fixed by removing the "Build Farm" and builder breadcrumbs so that they no longer appear in the location bar hierarchy. Instead, the location bar should look and work exactly the way it does on <https:/
It should still be obvious on a build machine page that you are in the build farm area, but the location bar should not be used to do this. A simple alternative would be to use a link, above the main heading on the build machine page, back to the build farm page. This is the same method used on secondary pages for a bug report (e.g. <https:/
Related branches
- Celso Providelo (community): Approve
-
Diff: 499 lines (+10/-180)16 files modifiedlib/lp/blueprints/browser/configure.zcml (+0/-1)
lib/lp/blueprints/browser/sprint.py (+0/-8)
lib/lp/bugs/browser/bug.py (+4/-2)
lib/lp/buildmaster/browser/builder.py (+0/-17)
lib/lp/buildmaster/browser/configure.zcml (+2/-6)
lib/lp/registry/browser/configure.zcml (+0/-2)
lib/lp/registry/browser/distribution.py (+0/-8)
lib/lp/registry/browser/product.py (+0/-9)
lib/lp/services/statistics/browser/launchpadstatistic.py (+1/-16)
lib/lp/soyuz/browser/build.py (+0/-9)
lib/lp/soyuz/browser/configure.zcml (+0/-4)
lib/lp/soyuz/browser/distroseriesbinarypackage.py (+0/-10)
lib/lp/translations/browser/configure.zcml (+3/-9)
lib/lp/translations/browser/pofile.py (+0/-9)
lib/lp/translations/browser/potemplate.py (+0/-61)
lib/lp/translations/browser/translationmessage.py (+0/-9)
Changed in soyuz: | |
status: | Unconfirmed → Confirmed |
description: | updated |
Changed in soyuz: | |
assignee: | nobody → mpt |
milestone: | none → 1.2.4 |
Changed in soyuz: | |
milestone: | 1.2.4 → none |
Changed in soyuz: | |
milestone: | none → 1.2.4 |
Changed in soyuz: | |
milestone: | 1.2.4 → 1.2.5 |
Changed in soyuz: | |
importance: | Undecided → Low |
milestone: | 1.2.5 → 1.2.6 |
Changed in soyuz: | |
milestone: | 1.2.6 → 1.99 |
Changed in soyuz: | |
milestone: | 1.99 → none |
description: | updated |
summary: |
- Build farm should not be a context (should not have tabs) + Build farm and build machines have their own unusable tabs |
Changed in soyuz: | |
assignee: | mpt → cprov |
Changed in soyuz: | |
milestone: | none → pending |
Changed in soyuz: | |
assignee: | Celso Providelo (cprov) → nobody |
Changed in launchpad: | |
assignee: | nobody → William Grant (wgrant) |
status: | Triaged → In Progress |
tags: |
added: qa-ok removed: qa-needstesting |
Changed in launchpad: | |
status: | Fix Committed → Fix Released |
The 3.0 version of the page in question here (https:/ /edge.launchpad .net/builders) doesn't suggest any relationship between the application tabs and the build farm, but it still doesn't behave like /+announcements, as in the latter the links on the application tabs are enabled. Which of them is the correct behavior?