customizing bug entry forum - making a simple one and a complex one

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

customizing bug entry forum - making a simple one and a complex one

mcmcom
Hi all,

just installed bugzilla and im working on configuring / customizing it.
I was wondering what the ideal solution for the following was:

1.  We have the default bug entry forum which is fine for our developers to use.   However we also have QA Tester users who are not very technically saavy.  I would like to make them a more basic version of the bug entry page.  with many of the fields removed (ie severity, etc) and a few new ones added.  I know how to customize the entry forums but what i want is to have Bugzilla determine what bug entry forum to display based on the users group or permissions.   So if they log in as a developer they get the standard bugzilla bug entry form, but if they log in as a QA tester they will get a simplifed entry form.

are there any best practices for this kind of thing?
TIA,
mcm
Reply | Threaded
Open this post in threaded view
|

Re: customizing bug entry forum - making a simple one and a complex one

Unca Ghryswald
mcmcom wrote
... if they log in as a developer they get the standard bugzilla bug entry form, but if they log in as a QA tester they will get a simplifed entry form.

are there any best practices for this kind of thing?
TIA,
mcm
Create each template separately to start.
When you have each template designed to your satisfaction, merge them and separate the DEV section from the QA section by using the group identifiers.  You can create a custom group if you need to.

Simple view of page would be:

[% process headers etc here %]

[% IF user.groups.DEV %]
   development template goes here
[% ELSE %]
    qa template goes here
[% END %]

[% process footers etc ehere %]

Might be an overly simplistic look at your problem, but that's how I would do it.  It's less messy than locking off each individual field within the single template, as you can just remove the larger block for QA later when your testers get more savvy...

best of luck,
Unca Ghrys