189613 - Bugzilla site needs a unified feature list

Status: RESOLVED FIXED

(Bugzilla :: bugzilla.org, enhancement, P3)

Description

[Joel Peshkin]

Developers attempting to sell their colleagues on a Bugzilla installation often
need a feature list to consult.  We should have one on the site.

Comment 1

[Dave Miller [:justdave]]

Good place to start is the recent status updates for all the new stuff since
2.16.  We'll need to do some work to enumerate the older stuff.

Comment 2

[Michael Morgan [:morgamic]]

I can drum something up (non-sarcastic) using the status updates as a starting
point -- I think having an example up will help get the ball rolling.

Comment 3

[Max Kanat-Alexander]

What sold Kerio on it was the Search -- almost every other tracking system has a
poor search feature, or one that is too basic. Oh, also, LDAP integration was
really helpful.

Comment 4

[Dave Miller [:justdave]]

This is sort of there now...

Except what's there sounds a lot like we're explaining the new features to
existing users of Bugzilla.  It needs to be reworded to explain the features to
people who have never seen it before.  "Bugzilla does this."  Instead of
"Bugzilla now does this." and "This new feature ...." etc.

We probably need to come up with some sort of markings on the features to
indicate which version they were introduced in.  Most of them on that existing
list are new in 2.18.  Especially now with 2.16 still being the released stable
version until we finalize 2.18, people need to know that stuff isn't available
in 2.16.

Comment 5

[Dave Miller [:justdave]]

Example:

>Authentication module/LDAP improvements
>
>Bugzilla's authentication mechanisms have been modularized, making
>pluggable authentication schemes for Bugzilla a reality. Both the
>existing database and LDAP systems were ported as part of modularization
>process. Additionally, the CGI portion of the backend was redesigned to
>allow for authentication from other sources, including (theoretically)
>email, which will help Bug 94850.
>
>As part of this conversion, LDAP logins now use Perl's standard
>Net::LDAP module, which has no external library dependencies.

Pluggable Authentication (new in 2.18)

Bugzilla features pluggable authentication modules, allowing sites to add
their own custom authentication procedures with minimal changes to the
core Bugzilla code.

The following authentication methods are shipped with Bugzilla:
  * Bugzilla's built-in database-backed authentication
  * LDAP authentication (using the Net::LDAP Perl module)

Comment 6

[Dave Miller [:justdave]]

and we need to not lose the existing page which is worded as if you're already
familiar with 2.16...  that should get moved somewhere as a "new in 2.18" page
available separately somewhere.

Comment 7

[Michael Morgan [:morgamic]]

the 2.18 features are a subset of the unified feature list, so I like the idea
of flagging things as "* -- new in 2.18!" and keeping them all on the same page.
 might be a little different scenario, but this is how some major manuals do it
(php, mysql, for example).

Comment 8

[Michael Morgan [:morgamic]]

*** Bug 255144 has been marked as a duplicate of this bug. ***

Comment 9

[Dave Miller [:justdave]]

OK, sounds like a plan.

Comment 10

[bigstijn]

Is the assigned person still working on this?

I think this is already implemented, with http://www.bugzilla.org/features/ .
But I maybe open a separate bug to add some specific topics to this page with information from
http://www.bugzilla.org/releases/2.22/new-features.html
http://www.bugzilla.org/releases/2.20/new-features.html
http://www.bugzilla.org/releases/2.18/new-features.html

Anyhow, http://www.bugzilla.org/features/ will need an update with bugzilla 3.0

Comment 11

[Dave Miller [:justdave]]

I kinda doubt morgamic's been working on this lately.  The new features vs existing features split did get made, but I don't think the existing features has gotten expanded much.  The new bug you filed seems to provide a more comprehensive view of what needs to be done there, so I think I'll go ahead and resolve this one.