|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
I've looked at this vishwas and tested re-assigning a loan (against clients only didnt try groups) to a different loan officer (in other words, chaning the loan officer of a loan(s)) - Seems to fit very well with what you described. can you confirm.
I did make some small changes in app and platform code after reviewing/testing.
I guess this handles the 'Bulk' case, the 'Single' case of re-assigning a loans loan officer should be handled similarly as its an important area especially with respect to https://mifosforge.jira.com/browse/MIFOSX-73. So guess what I am saying is, its a seperate operation on a loan to 're-assign' loan office and general update/modify functionality of a loan shouldnt allow change of loan officer. should come through its own operation.