Bugzilla:BzAPI:Objects:Configuration: Difference between revisions

Bugzilla:BzAPI:Objects:Configuration (view source)

544 bytes added , 20 October 2009

no edit summary

Account confirmers, Anti-spam team, Confirmed users, Bureaucrats and Sysops emeriti

4,925

edits

@@ Line 7: / Line 7: @@
 * The use of hashes also gives forwards-compatibility. For example, if some fields became product or component-specific, we could add a "fields" member to the hash.
 * Classifications are not wrapped around their products in the same way that products are wrapped around their components because the use of classifications is optional, and this would make the top-level field name depend on whether they were switched on or not.
+====Open Questions====
+* Are there any more params we should expose, like maxattachmentsize?
+* Are there any more hashes, apart from flag_types, which should be keyed by ID rather than name? Should we be using group IDs rather than names?
+* Should request_group and grant_group on flag_types be Arrays rather than Strings, for forwards-compatibility?
+* Is an "is_for_bugs" boolean the right way of doing the bug vs. attachment choice?
+* Does is_on_bug_entry make much sense if a Bugzilla has multiple bug entry templates?
 ==Configuration==
@@ Line 67: / Line 75: @@
 |id||Integer||
 |-
-|flag_type||Array of Integer||IDs of flag types settable in this component
+|flag_type||Array of Integer||IDs of flag types settable on bugs/attachments in this component
 |}