889: Template for bug-tracker integration is very hard to find for new admin

ted.d******@gmai***** (Google Code) (Is this you? Claim this profile.)
Sept. 21, 2009 
The bug tracker url template is located under the repository configuration.
 This took me an hour to find and I only found it because I knew it existed
and started clicking *everything* to find it.  

In a related issue, I only clicked on the repository name by accident. 
There was no clue that there was more configuration to be done other than
that showing in the table.

I think it would help if the bug tracker template were moved to the general
settings.  It isn't really related to the SCM repository in any meaningful way.
chipx86
#1 chipx86 
It actually is related to the repository.

Many of the larger setups out there host a number of different repositories, and
these are tied to repositories. For example, we host Google Summer of Code projects,
where each repository represents a project, and has its own bug tracker.

In the future we may be able to make this more flexible and store bug trackers
separately from repositories, making it possible to link one repository to many
trackers or vice-versa more easily. But that would be post-1.0.
  • -Type-Defect
    -Priority-Medium
    +Type-Enhancement
    +Priority-Low
    +Milestone-Release1.5
    +Component-Integration
#2 ted.d******@gmai***** (Google Code) (Is this you? Claim this profile.) 
OK.  That is a fair view of the world.

Can the existence of the template be signaled?  Perhaps by adding a column to the
table summarizing the repositories?

Or could there by a little edit pencil in a column that has a header of "Change
hidden stuff that we didn't really want you to know about"?
chipx86
#3 chipx86 
We can certainly add a column. That should be easy to do.

I'm working on new documentation that does go into this in some detail. It should be
a little easier at least to figure this out from the manual.

I'm also hoping to introduce some more streamlined admin UI modifications post-1.0.
  • +Confirmed
#4 ted.d******@gmai***** (Google Code) (Is this you? Claim this profile.) 
I generally think that discoverability is better than a manual.

Nifty software, btw.
chipx86
#5 chipx86 
I agree. We're just not at a point where we can do an overhaul of the admin UI to
make this more clear. I'm definitely hoping to down the road though.
#6 ted.d******@gmai***** (Google Code) (Is this you? Claim this profile.) 
Even a wee bit of text on that page would help.  "Click on the repository to edit the
following additional parameters: ...."
chipx86
#7 chipx86 
This is a lot more straight-forward now in 1.1 dev. A lot of the time, with many
setups, admins won't have to even deal with the bug tracker anymore. When configuring
the repository with known services (like Trac, SourceForge, etc), the bug tracker
information will be populated automatically. This was added in r2080.

I'll keep this open for further future improvements, but I'd like to know your
opinion on the new UI in 1.1.
david
#8 david 
I think this is sufficiently awesome now to call this fixed. If we have ideas for
future improvements, we can file new enhancement requests.
  • -Confirmed
    +Fixed