Unclear when adding a bug tracker whether the URL is for the project or their tracker

Bug #4534 reported by Brad Bollenbach
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

From an email exchange with Alex Ross, of Nexenta fame:

---
A minor usability comment.. Somehow I stumbled when entering the bug tracker URL, didn't know what to choose: Trac's home page or our own Trac's database. It's ambiguous.
---

We could probably add an example to explain this more clearly...maybe even an error message if the user tries to enter the homepage URL of the bug tracker itself (rather than the URL to their instance of the bug tracker?)

Brad Bollenbach (bradb)
Changed in malone:
assignee: nobody → bradb
status: New → Accepted
Changed in malone:
assignee: bradb → nobody
Revision history for this message
Bryce Harrington (bryce) wrote :

I'm not sure I understand this bug report, could you elaborate further? Steps to reproduce the problem, and suggested wording for the improved explanation would help immensely. Thanks ahead of time!

Changed in malone:
status: Triaged → Incomplete
Curtis Hovey (sinzui)
Changed in malone:
status: Incomplete → Triaged
Revision history for this message
Curtis Hovey (sinzui) wrote :

This is a serious bug and the help and validation rules in the bug tracker widget encourage users to register duplicate bug trackers, or ones that do not work.

The problem is that the bug tracker registration form does not state if the bug tracker type uses the remote_product field from IProduct so that many projects may use the same bug tracker. Bug trackers were in fact conceived to do this...other wise the bug tracker would have been a simple field on IProduct. Some bug trackers really do need the project, but it is not clear how to specify that, or even if query parameters re needed.

Examples that I have learned from experience, not documentation or even code:
  * bugzilla uses remote_product. GNOME's bug tracker is of this type
    each gnome project can choose the gnome bug tracker and set the remote_product
  * source forge uses remote_product, and falls back to IProduct.sfproduct
    each project that uses source forge for bug tracking only needs to choose the existing bug tracker
    and provide either of those fields.

So while there should be only one bug tracker each with gnome.org and sourceforge.net in the url, we have hundreds. Users include the project's name in the url, some include query parameters.

So when registering a bug tracker do I use bugs.example.org or bugs.example.org/my-project? I do not know because the form does not explain the expected URL when I choose a bug traker type, it does not validate either, so I have to report a bug or ask a question to discover I setup the bug tracker wrong.

tags: removed: trivial
summary: - The URL required for registering a new bugtracker should be
- disambiguated
+ Unclear when adding a bug tracker whether the URL is for the project or
+ their tracker
Changed in launchpad:
importance: Medium → Low
tags: added: easy
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.