Hi CPH,
CPHennessy schrieb:
Hi all,
I've just had to entry a bug report and it is quite an unpleasant
experience :
http://qa.openoffice.org/issue_handling/submission_gateway.html
I do have this in moste cases, but for completely different reasons. I'd
like to go directly to the plain IssueZilla form, as only there I could
put in all the things I want (an relaay need).
Well .. I'm not the typical OOo user anyway. But I'd agree to Christian,
that a two-way approach was the best (very simple interface vs. complete
issuezilla form).
There are too many choices for and this only scares way many potential bug
reporters (Obviously if we do not want those reports... )
the problem is, that even with a simplified interface, we would need
some data, that are mandatory from IssueZilla's perspective. Some of
them (like subcomponent) cannot easily be set to a default, as they are
configurable within IssueZilla (per component). And we do not have
API-level access to IssueZilla (so the only way to ask IssuZilla about
it's configuration is to go through the web interface).
Assuming we do want those reports, I think that some changes need to be made
to the above page. What I suggest is to provide a javascript interface where
the user is brought thru a number of obvious steps :
I'd rather see a very simple interface, that only asks for the most
relevant data and leaves default values, where possible.
1) choose from : installation, writer, calc, impress, database, printing,
upgrading, other (e.g. web, other langs, ... ? )
This would be the "Component". I'd suggest, we have only the "per
Application" settings there
2) choose version ( latest version being the default - with links to download
it).
why download? (well .. we could a download link to the form .. but I
don't se the sense)
as we are speaking of a very simple interface, I'd only list released
final versions there (no developer snapshots...)
4) issue type should only be a choice between "bug" or "new feature"
Leave only bug. So we could make clear, how to submit *bugs* (I get
requests form time to time, that people cannot identify "issue" as the
way to submit bugs .. and tat's what they want to do in most cases)
5) OS ( set by default from what the browser sends)
6) Summary
7) Description
8) "Submit issue"
Things which do *not* need to be shown for the "simple user" :
- on the main page :
- software components
- by project
- by language
- by code module
+1
- on the "Enter issue" page
- subcomponent
Unfortunately mandatory. It might be set to the "ui" default, but
subcomponents are unter review and might change .. so that's the real
problem to me.
- initial state
defaults to unconfirmed
- assigned to
is derived from component / sumbcomponent .. no neet to put it in
- platform
- priority
should default to 3 maybe a checkbox "crash occures" that would raise
prio to 2
- cc:
Opinions ?
As said .. I'd prefere two interfaces. But these nedd to be maintained.
So I'd like to see Frank's opinion, who is maintaining the gateway page
at the moment.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
