Ticket #2140 (closed unplanned_task)

Opened 10 years ago

Last modified 10 years ago

BUG_REPORT_FORM_R0

Reported by: deyan Owned by: deni
Priority: major Milestone: X2
Component: uncategorized Version: 2.0
Keywords: Cc:
Category: unknown Effort:
Importance: Ticket_group:
Estimated Number of Hours: 0 Add Hours to Ticket: 0
Billable?: yes Total Hours: 0
Analysis_owners: deyan Design_owners: deni
Imp._owners: deni Test_owners:
Analysis_reviewers: Changelog:
Design_reviewers: tsachev Imp._reviewers: tsachev, pap
Test_reviewers: Analysis_score: 0
Design_score: 3.5 Imp._score: 3
Test_score: 0

Description

Change History

comment:1 Changed 10 years ago by deyan

  • Owner set to deyan
  • Status changed from new to s1a_analysis_started

comment:2 Changed 10 years ago by deni

  • Status changed from s1a_analysis_started to s1b_analysis_finished

comment:3 Changed 10 years ago by dido

  • Status changed from s1b_analysis_finished to s1c_analysis_ok

Analysis looks fine. However note that in design section must be mentioned exactly which of the fields should be required(if any) and which should be optional for the user to send.
Also if the attached file is too big, there should be indication for uploading, sending progress etc. And there should be a message whether the report was send successfully or not. If we are able to add part of this functionality in this revision it will be lovely.
Analysis Reviewed 3.5p (10m)

comment:4 Changed 10 years ago by deni

  • Design_owners set to deni
  • Owner changed from deyan to deni
  • Status changed from s1c_analysis_ok to s2a_design_started
  • Imp._owners set to deni

comment:5 Changed 10 years ago by deni

  • Status changed from s2a_design_started to s2b_design_finished

comment:6 Changed 10 years ago by tsachev

  • Status changed from s2b_design_finished to s2c_design_ok
  • Design_score changed from 0 to 3.5
  • Design_reviewers set to tsachev

Configuration

The bug report address must be configurable. Can you use the configuration module for this?

Multipart request

I think that ConnectionUtil is not a good idea. There is more than enough static code in sophie2.
It is better to create a MultiparRequest class which can be used as follwing

String urlAddress;// The address
String[] paramNames;// The names
Object[] paramValues;// The values
MultiparRequest request = new MultiparRequest(urlAddress, paramNames, paramValues);
try {
  String response = request.send();
} catch (IOException e) {
  // Handle exception logic
}

sophie2.org stuff

  • What is the response returned by the server (php script)?
  • There is nothing about how you plan to implement the server side logic - php/sql stuff. Why php and what database will you use. Postgresql is a good choice, mysql too, but you have to propose one, and with a reason.
  • The php code and schema for the database must be added under version control, however they are not part of sophie2-platform so we need to create a new folder in svn as is manage to hold sophie2.org resources. We may call it server-config or something else. The applet configuration, cert creation, hudson scripts should also be there but it is not related with this task. However php and sql stuff are. Maybe pap can help with svn configuration.

comment:7 Changed 10 years ago by deni

  • Status changed from s2c_design_ok to s3a_implementation_started

comment:8 Changed 10 years ago by deni

  • Status changed from s3a_implementation_started to s3b_implementation_finished

comment:9 Changed 10 years ago by pap

  • Status changed from s3b_implementation_finished to s3c_implementation_ok
  • Imp._score changed from 0 to 3
  • Imp._reviewers set to tsachev, pap
  • Accepted ang attaches files copied to appropriate locations
  • There were some fixes especially to the php code and its configurability
  • The bug report dialog looks bad as internal design.

comment:10 Changed 10 years ago by deyan

  • Status changed from s3c_implementation_ok to closed

Batch update from file query-10.csv

Note: See TracTickets for help on using tickets.