We intend to change the also-affect use-cases. They are legitimate to add a bug task, but most cases users want to retartget, which is not supported. We intend to support retargeting in the next few months. Most users do not know what "upstream" or "downstream" is. We have had to remove those words, or explain them in detail. Consider that this link is also shown on projects and the bug may not actually be upstream or downstream. The user really is adding a project or distro+sourcepackage bug task, not an upstream/downstream task.
The link rendering code supports titles attributes. You can pass the 'summary' kwarg to the Link() contructor to provide a title attribute. The 'addupstream' method of BugContextMenu in lib/lp/bugs/browser/bugs.py needs the summary. Actually, most of the link in the menu appear to be missing the summary attribute :(
We intend to change the also-affect use-cases. They are legitimate to add a bug task, but most cases users want to retartget, which is not supported. We intend to support retargeting in the next few months. Most users do not know what "upstream" or "downstream" is. We have had to remove those words, or explain them in detail. Consider that this link is also shown on projects and the bug may not actually be upstream or downstream. The user really is adding a project or distro+ sourcepackage bug task, not an upstream/downstream task.
The link rendering code supports titles attributes. You can pass the 'summary' kwarg to the Link() contructor to provide a title attribute. The 'addupstream' method of BugContextMenu in lib/lp/ bugs/browser/ bugs.py needs the summary. Actually, most of the link in the menu appear to be missing the summary attribute :(