[jira] [Updated] (FINERACT-199) Ability to undo a client transfer
[ https://issues.apache.org/jira/browse/FINERACT-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-199: Labels: beginner p2 starter (was: p2) > Ability to undo a client transfer > - > > Key: FINERACT-199 > URL: https://issues.apache.org/jira/browse/FINERACT-199 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Reporter: Dayna Harp >Assignee: Markus Geiss >Priority: Minor > Labels: beginner, p2, starter > > https://mifosforge.jira.com/browse/MIFOSX-1489 > Our clients want to have the ability to undo a client transfer. cases when > this will be needed. An example will be after you transfer a client and > realized you need to adjust a payment made before the transfer. This > functionality will allow you to undo the transfer and make adjustment to the > payment. In case a transaction has been made after the transfer. The client > has to reversed this transaction him or herself before undoing the client > transfer -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-269) Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and Recuring Deposit Account
[ https://issues.apache.org/jira/browse/FINERACT-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-269: --- Assignee: (was: Markus Geiss) > Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and > Recuring Deposit Account > --- > > Key: FINERACT-269 > URL: https://issues.apache.org/jira/browse/FINERACT-269 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Reporter: Ippez Roberts >Priority: Major > Labels: Fineract-CN, gsoc, p2 > Attachments: Infobase.pdf > > > Infobase > This allows you to add free-form descriptions or notes to certain accounts. > These notes can be unlimited in size and can be used to provide all kind of > additional information about any account or its owner. > Later then whenever this account will be accessed this information will be > displayed on the screen as in following example. > See attachment for visual explanation > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-264) Document the address Module
[ https://issues.apache.org/jira/browse/FINERACT-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-264: Labels: beginner document easytask starter (was: beginner document easytask) > Document the address Module > --- > > Key: FINERACT-264 > URL: https://issues.apache.org/jira/browse/FINERACT-264 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Reporter: Nikhil Pawar >Priority: Trivial > Labels: beginner, document, easytask, starter > Original Estimate: 24h > Remaining Estimate: 24h > > Address Module has been newly integrated into Apache Fineract. Document its > usage and configuration by using mocks and configuration steps -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-420) Phase 2 of Credit Bureau Integration with Apache Fineract
[ https://issues.apache.org/jira/browse/FINERACT-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-420: --- Assignee: (was: Markus Geiss) > Phase 2 of Credit Bureau Integration with Apache Fineract > - > > Key: FINERACT-420 > URL: https://issues.apache.org/jira/browse/FINERACT-420 > Project: Apache Fineract > Issue Type: New Feature > Components: Client, Loan >Reporter: Ed Cable >Priority: Major > Labels: gsoc2017 > > This project would extend off of the initial work that was done in 2016 > during Google Summer of Code led by Nikhil Pawar under the mentorship of > Nayan as outlined at > https://mifosforge.jira.com/wiki/spaces/projects/pages/134905860/Mifos+Credit+bureau+Integration+Risk+calibration+Module+RCM+ > During that project, Nikhil completed the initial version of the integration > with data flowing back and forth between Apache Fineract and two credit > bureaus for India - Highmark and Equifax and a client address module for the > web app. > Phase 2 will continue extending the existing architecture to allow more > seamless flow of data from Fineract to the credit bureaus on a regular basis > and the option for staff to pull clients information from the credit bureau > whenever they'd like. Project will also focus on genericizing and extending > the integration to support credit bureaus in Sub-Saharan Africa, SE Asia, and > Latin America. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINCN-203) Checking for Camera Permission instead of Write Permission in CustomerProfileActivity
[ https://issues.apache.org/jira/browse/FINCN-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051855#comment-17051855 ] Prajwal S Belagavi commented on FINCN-203: -- PR done. Yet to be reviewed. > Checking for Camera Permission instead of Write Permission in > CustomerProfileActivity > - > > Key: FINCN-203 > URL: https://issues.apache.org/jira/browse/FINCN-203 > Project: Fineract Cloud Native > Issue Type: Bug > Components: fineract-cn-mobile >Reporter: Prajwal S Belagavi >Priority: Minor > Attachments: FINCN-203.mp4 > > Original Estimate: 1h > Remaining Estimate: 1h > > # Click on "Customer" in side drawer. > # Click on any item in list of customers. > # Click on the profile picture (by default it's the Mifos Logo) > # Click on "Share" option in the appbar. > # Supposing the permission to write to external storage is not given, it'll > ask for permission. When granted it should ideally call the "shareImage" > method, but nothing happens. This is because when the Permission is being > granted, it's checking for "CAMERA" permission instead of > "WRITE_EXTERNAL_STORAGE" permission. > It occurs when the permission is being granted initially and later, this > error does not occur. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-525) Search for a Member by ID when adding to Group
[ https://issues.apache.org/jira/browse/FINERACT-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-525: --- Assignee: (was: Markus Geiss) > Search for a Member by ID when adding to Group > -- > > Key: FINERACT-525 > URL: https://issues.apache.org/jira/browse/FINERACT-525 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Groups >Reporter: May Myint >Priority: Minor > Labels: beginner, gsoc, p2, starter > > When associating new Clients to a Group through Manage Members, clients can > only be searched by name. The issue is that it is possible for there to be > many clients with the same name. Thus the user will have to select the > clients one by one to get the right person. > Allowing for the client to be searched by Client # would be more efficient. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-525) Search for a Member by ID when adding to Group
[ https://issues.apache.org/jira/browse/FINERACT-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-525: Labels: beginner gsoc p2 starter (was: gsoc p2) > Search for a Member by ID when adding to Group > -- > > Key: FINERACT-525 > URL: https://issues.apache.org/jira/browse/FINERACT-525 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Groups >Reporter: May Myint >Assignee: Markus Geiss >Priority: Minor > Labels: beginner, gsoc, p2, starter > > When associating new Clients to a Group through Manage Members, clients can > only be searched by name. The issue is that it is possible for there to be > many clients with the same name. Thus the user will have to select the > clients one by one to get the right person. > Allowing for the client to be searched by Client # would be more efficient. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-528) After taking survey for a client, Survey is displaying score of each question in stead of total score of each survey
[ https://issues.apache.org/jira/browse/FINERACT-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-528: --- Assignee: (was: Nazeer Shaik) > After taking survey for a client, Survey is displaying score of each question > in stead of total score of each survey > > > Key: FINERACT-528 > URL: https://issues.apache.org/jira/browse/FINERACT-528 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Surveys >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, beginner, p1, starter > Fix For: 1.5.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-528) After taking survey for a client, Survey is displaying score of each question in stead of total score of each survey
[ https://issues.apache.org/jira/browse/FINERACT-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-528: Labels: 2019-mifos-gsoc Volunteer beginner p1 starter (was: 2019-mifos-gsoc GSOC Volunteer gsoc p1) > After taking survey for a client, Survey is displaying score of each question > in stead of total score of each survey > > > Key: FINERACT-528 > URL: https://issues.apache.org/jira/browse/FINERACT-528 > Project: Apache Fineract > Issue Type: Improvement > Components: Client, Surveys >Affects Versions: 1.1.0 >Reporter: Santosh Math >Assignee: Nazeer Shaik >Priority: Major > Labels: 2019-mifos-gsoc, Volunteer, beginner, p1, starter > Fix For: 1.5.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-538) The updated_on or created_on columns in m_client and m_address tables are not populated
[ https://issues.apache.org/jira/browse/FINERACT-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-538: Labels: beginner starter (was: GSOC) > The updated_on or created_on columns in m_client and m_address tables are not > populated > --- > > Key: FINERACT-538 > URL: https://issues.apache.org/jira/browse/FINERACT-538 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Affects Versions: 1.0.0 >Reporter: thynn win >Priority: Major > Labels: beginner, starter > > The updated_on or created_on columns in m_client and m_address tables are not > populated. > These fields should be populated when records are created and updated. This > will help with reporting as client list can grow and they can search by date > range. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINERACT-538) The updated_on or created_on columns in m_client and m_address tables are not populated
[ https://issues.apache.org/jira/browse/FINERACT-538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick reassigned FINERACT-538: --- Assignee: (was: Markus Geiss) > The updated_on or created_on columns in m_client and m_address tables are not > populated > --- > > Key: FINERACT-538 > URL: https://issues.apache.org/jira/browse/FINERACT-538 > Project: Apache Fineract > Issue Type: Improvement > Components: Client >Affects Versions: 1.0.0 >Reporter: thynn win >Priority: Major > Labels: GSOC > > The updated_on or created_on columns in m_client and m_address tables are not > populated. > These fields should be populated when records are created and updated. This > will help with reporting as client list can grow and they can search by date > range. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (FINERACT-749) Client family member date of birth min value set to current year
[ https://issues.apache.org/jira/browse/FINERACT-749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Awasum Yannick updated FINERACT-749: Labels: GCI-2019 beginner starter (was: GCI-2019) > Client family member date of birth min value set to current year > > > Key: FINERACT-749 > URL: https://issues.apache.org/jira/browse/FINERACT-749 > Project: Apache Fineract > Issue Type: Bug > Components: Client >Affects Versions: 1.3.1 >Reporter: Sidhant Gupta >Priority: Major > Labels: GCI-2019, beginner, starter > Fix For: 1.5.0 > > > The date of birth value for client family member cannot be set to less than > the first date of the current year. It can be fixed by modifying the input > tag's `min` attribute. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINCN-203) Checking for Camera Permission instead of Write Permission in CustomerProfileActivity
[ https://issues.apache.org/jira/browse/FINCN-203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051852#comment-17051852 ] Prajwal S Belagavi commented on FINCN-203: -- I'll be working on it. > Checking for Camera Permission instead of Write Permission in > CustomerProfileActivity > - > > Key: FINCN-203 > URL: https://issues.apache.org/jira/browse/FINCN-203 > Project: Fineract Cloud Native > Issue Type: Bug > Components: fineract-cn-mobile >Reporter: Prajwal S Belagavi >Priority: Minor > Attachments: FINCN-203.mp4 > > Original Estimate: 1h > Remaining Estimate: 1h > > # Click on "Customer" in side drawer. > # Click on any item in list of customers. > # Click on the profile picture (by default it's the Mifos Logo) > # Click on "Share" option in the appbar. > # Supposing the permission to write to external storage is not given, it'll > ask for permission. When granted it should ideally call the "shareImage" > method, but nothing happens. This is because when the Permission is being > granted, it's checking for "CAMERA" permission instead of > "WRITE_EXTERNAL_STORAGE" permission. > It occurs when the permission is being granted initially and later, this > error does not occur. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINCN-203) Checking for Camera Permission instead of Write Permission in CustomerProfileActivity
Prajwal S Belagavi created FINCN-203: Summary: Checking for Camera Permission instead of Write Permission in CustomerProfileActivity Key: FINCN-203 URL: https://issues.apache.org/jira/browse/FINCN-203 Project: Fineract Cloud Native Issue Type: Bug Components: fineract-cn-mobile Reporter: Prajwal S Belagavi Attachments: FINCN-203.mp4 # Click on "Customer" in side drawer. # Click on any item in list of customers. # Click on the profile picture (by default it's the Mifos Logo) # Click on "Share" option in the appbar. # Supposing the permission to write to external storage is not given, it'll ask for permission. When granted it should ideally call the "shareImage" method, but nothing happens. This is because when the Permission is being granted, it's checking for "CAMERA" permission instead of "WRITE_EXTERNAL_STORAGE" permission. It occurs when the permission is being granted initially and later, this error does not occur. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink
[ https://issues.apache.org/jira/browse/FINERACT-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051641#comment-17051641 ] Awasum Yannick commented on FINERACT-849: - [~edcable], Did you want to frame this as a GSoC 2020 project? > Migrate Fineract ORM from OpenJPA to EclipseLink > > > Key: FINERACT-849 > URL: https://issues.apache.org/jira/browse/FINERACT-849 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Ed Cable >Priority: Major > > In line with the rationale for choosing EclipseLink as the ORM replacement > for Hibernate in FineractCN, we have broad consensus across the community to > swap out OpenJPA with EclipseLink. > OpenJPA seems to have reached its end of life with community activity > withering and the trade-offs between Hibernate and EclipseLink are much > lower. We also have community members who are migrating Fineract 1.x to > PostGreSQL and would benefit from the increased performance with EclipseLink. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (FINERACT-849) Migrate Fineract ORM from OpenJPA to EclipseLink
Ed Cable created FINERACT-849: - Summary: Migrate Fineract ORM from OpenJPA to EclipseLink Key: FINERACT-849 URL: https://issues.apache.org/jira/browse/FINERACT-849 Project: Apache Fineract Issue Type: Improvement Reporter: Ed Cable In line with the rationale for choosing EclipseLink as the ORM replacement for Hibernate in FineractCN, we have broad consensus across the community to swap out OpenJPA with EclipseLink. OpenJPA seems to have reached its end of life with community activity withering and the trade-offs between Hibernate and EclipseLink are much lower. We also have community members who are migrating Fineract 1.x to PostGreSQL and would benefit from the increased performance with EclipseLink. -- This message was sent by Atlassian Jira (v8.3.4#803005)
