[ 
http://mifosforge.jira.com/browse/MIFOS-3301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kalyan Akella updated MIFOS-3301:
---------------------------------

    Description: 
Inside latest-schema.sql, all the tables whose storage engine is either 
unspecified or is different from 'InnoDB', must be migrated to the 'InnoDB' 
storage engine format.



  was:
As an Admin
I WANT TO add questions to a section (while creating a section)
SO THAT Questions can be grouped into specific sections for display purpose.

Acceptance Criteria:

1a. ENSURE that a list box with all the questions that are active in the system 
is displayed. Admin should be able 
    to multi select the questions. The questions should appear in alphabetical 
order. 

--- Kindly provide a scroll bar for the list box. (Expect about 200 questions 
to be active in the system.)

1b. Given that the admin has provided a valid title to the QG,
   WHEN the admin clicks the ADD button without any section in the text box,
   THEN a section called MISCELLANEOUS along with the questions selected should 
appear beneath.
   See screenshot for reference.

2. When an admin provides a valid section name in the text box and clicks ADD 
button,
   THEN a section with the name as provided along with the questions selected 
should appear beneath.

3. Ensure the section last added appears on top of the section beneath.

4. If a section with an existing section name is provided, then no duplicate 
section should be added beneath AND also
   NO validation message should be provided to the user. IN ADDITION, the 
questions selected from the list box  should appear under the existing section.
5. Each question associated with a QG should be appended with a remove link so 
that the question can be 
   disassociated with the section.

6. The sections along with corresponding questions added whilst creating the QG 
should be available for view while   
   viewing the QG details.

    Component/s:     (was: Surveys/PPI)
                 Database

> TECH: Migrate all tables in MIFOS to InnoDB storage engine
> ----------------------------------------------------------
>
>                 Key: MIFOS-3301
>                 URL: http://mifosforge.jira.com/browse/MIFOS-3301
>             Project: mifos
>          Issue Type: Story
>          Components: Database
>    Affects Versions: Release E - Iteration 2
>            Reporter: Kalyan Akella
>            Assignee: Kalyan Akella
>            Priority: Major
>             Fix For: Release E - Iteration 2, Release E
>
>
> Inside latest-schema.sql, all the tables whose storage engine is either 
> unspecified or is different from 'InnoDB', must be migrated to the 'InnoDB' 
> storage engine format.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to