bugzilla 3.0...

[Joel Peshkin]

Jason Pyeron wrote:

>
>I ask because we just took on a contract.
>
>We have to provide:
>
> security acl's for each aspect
>
> product/process trees (ie component/subcomponet...)
>  queries on above or subspecs of above
>
> customizable state changes (status/resolutions)
>  
> rich content in the comments (uml/etc)
>
> iso 9001 concerns addressed
>
> api's for integration with other systems (tightly)
>  salesforce system
>  techsupport / customer service system 
>  accounting system
>  enterprise signon system
>
> partition / linkage for different classifications of data security
>
>  none / NDA / sensitive / secret / top secret 
>   compartments etc.
>
> audit logs on usage / access
>
> email intgration, etc...
> http access / thin client
>
>
>That being said we would like to back port it when it is done. Also we are 
>looking at license models. It boils down to marketing vs development.
>
>-jason pyeron
>  
>

Jason,

    That fits very well with my employer's roadmap.   I'd suggest 
developing those against the 2.17 "tip"

    The interesting features I am contemplating that seems to go in the 
same direction are....

acls for each aspect (including acls for custom fields)
iso9001 considerations addressed (a minimum of root-cause tracking) also 
a way to link bugs to a corrective action when one is indicated
some improvment to the product/component hierarchy
tying bug resolutions into a "solution" database.
integration with enterprise signon.  [both LDAP and Single-signon] Also, 
permit Bugzilla groups to include groups from external systems [LDAP, 
other databases...]

-Joel