Merge lp:~jcsackett/launchpad/private-bugs-404 into lp:launchpad
Status: | Merged |
---|---|
Approved by: | Данило Шеган |
Approved revision: | no longer in the source branch. |
Merged at revision: | 12847 |
Proposed branch: | lp:~jcsackett/launchpad/private-bugs-404 |
Merge into: | lp:launchpad |
Diff against target: |
89 lines (+39/-4) 3 files modified
lib/lp/bugs/browser/tests/test_bug_views.py (+26/-0) lib/lp/bugs/templates/bug-portlet-actions.pt (+1/-1) lib/lp/bugs/templates/bugtask-index.pt (+12/-3) |
To merge this branch: | bzr merge lp:~jcsackett/launchpad/private-bugs-404 |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Данило Шеган (community) | Approve | ||
Review via email: mp+57244@code.launchpad.net |
Commit message
[incr] [r=danilo][bug=434733] Fixes links to private bugs so that they're only text if the user can't see the bug.
Description of the change
Summary
=======
When a public bug is marked as a duplicate of a private bug, the duplicate listings in the portlet do not provide links, just text. However, the warning below the page links to the private bug, which then yields a 404. We shouldn't generate 404ing links if we can avoid it.
This just changes that link text to regular text when the user can't see the master bug, and adds a test to ensure that it's working.
Preimplementation
================
Spoke with Curtis Hovey
Implementation
==============
lib/lp/
-------
Test
lib/lp/
-------
Altered dupe link in the warning above the comment box to only create a link if the master bug is viewable by the user, and just show the text otherwise.
Tests
=====
QA
==
Find (or create) a public duplicate of a private bug--the warning before the comment form should list the private bug, but should not link to it.
Lint
====
make lint output:
= Launchpad lint =
Checking for conflicts and issues in changed files.
Linting changed files:
lib/lp/
lib/lp/
This is good, but possibly incomplete.
If the master bug isn't viewable, perhaps we shouldn't list the bug against- private- bugs, and similarly in the planning for bug
number *either* - the whole point being that said bug is invisible to
the submitter. We've a cluster of bugs around the behaviour and UI of
duplicates-
relationships and better privacy, the idea was put forward to simply
hide relationships (of which duplicate is one that we already have)
where the other side was invisible to the viewing user.
Hmm, in writing this I realise that actually the thing is way to
complex to shoe-horn in here.
But I do think we should do something to help with the support load -
folk will be confused when its not a link and they can't see it.
Perhaps 'duplicate of bug 42 which is embargoed (you cannot view it)'.
Or something.