[ 
http://mifosforge.jira.com/browse/MIFOSDEPLOY-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59510#action_59510
 ] 

Ryan Whitney commented on MIFOSDEPLOY-143:
------------------------------------------

This is now happening for all migrated templates

> Clients are not appearing under the Group for MDB1_ROYGAPROSTA_THU_CTR1.xlsx
> ----------------------------------------------------------------------------
>
>                 Key: MIFOSDEPLOY-143
>                 URL: http://mifosforge.jira.com/browse/MIFOSDEPLOY-143
>             Project: mifos deployments
>          Issue Type: Bug
>          Components: Data Migration - Client Accounts
>            Reporter: Ryan Whitney
>            Assignee: Seetha Rajagopalan
>            Priority: Critical
>
> I tried migrating the template "MDB1_ROYGAPROSTA_THU_CTR1.xlsx" (Dropbox -> 
> KMBI data share -> Metro Davao 1 -> New Set), and it imported fine, but the 
> clients do not appear under the group when looking at the group details.
> REPRO:
> 1. Migrate MDB1_ROYGAPROSTA_THU_CTR1.xlsx
> 2. Search for clients
> 3. Click on the group to see group details
> EXPECTED:
> See a list of clients for the group
> ACTUAL:
> No clients are displayed
> Note: This did not repro with migrating a different template.  Also, the 
> clients show up as assigned to the group, but just don't appear under the 
> group

-- 
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 

Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev 
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to