[jira] [Commented] (FINCN-352) Fineract Improvement Proposals
[
https://issues.apache.org/jira/browse/FINCN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17420895#comment-17420895
]
Myrle Krantz commented on FINCN-352:
Note also that this is not the way we write issues: An issue should be a task
that can be solved by an individual, usually via a code commit or an action
within our infrastructure.
> Fineract Improvement Proposals
> --
>
> Key: FINCN-352
> URL: https://issues.apache.org/jira/browse/FINCN-352
> Project: Fineract Cloud Native
> Issue Type: Improvement
>Reporter: Saransh Sharma
>Priority: Major
>
> Purpose
> The purpose of a Fineract CN Improvement Proposal (FIP) is to introduce any
> major change into Fineract CN. This is required in order to balance the need
> to support new features, uses cases , automation . Given the nature of the
> project that is micro services and its functional implications. To be able to
> bring changes in core libs and changes in the core services.
> What is considered as major change?
> Any of the following should be considered a major change:
> * Any major new feature, subsystem, or piece of functionality
> * Any change that removes the core lib
> * Design patterns changes that may take away the way project interact with
> respect to the services and db
> * Removal of services and core libs
> * Adding a new type and frameworks
> * Adding external service like automation and boilerplates
> * Architectural changes overhaul like moving service or merging service in
> single piece
> What should be included in the FIP
> * Motivation: describe the problem to be solved.
> * Proposed Change: describe the new thing you want to do. This may be fairly
> extensive and have large subsections of its own. Or it may be a few
> sentences, depending on the scope of the change.
> * New or Changed Public Interfaces: impact to any of the "compatibility
> commitments" described above. We want to call these out in particular so
> everyone thinks about them.
> * New dependencies: describe any third-party libraries that the feature will
> require, from PyPI or NPM. In particular, make sure their license is
> compatible with the [Apache License v2.0]
> ([https://www.apache.org/licenses/LICENSE-2.0]).
> * Migration Plan and Compatibility: if this feature requires additional
> support for seamless upgrades describe how that will work. In particular,
> it’s important to mention if:
> ** The feature requires a change in some way to core libs
> ** Some API level change
> ** Removing some lib or its generation
> ** The feature will coexist with similar functionality for some period of
> time, allowing for a deprecation period.
> * Rejected Alternatives: What are the other alternatives you considered and
> why are they worse? The goal of this section is to help people understand why
> this is the best solution now, and also to prevent churn in the future when
> old alternatives are reconsidered.
> Who should initiate FIP
> Anyone can initiate a FIP, but preferably someone with the intention of
> implementing it.
> Process
> # [Create an issue|https://github.com/apache/incubator-superset/issues] with
> the prefix “[FIP]” in the title. The issue will be tagged as “fip” by a
> committer, and the title will be updated with the current SIP number.
> # Notify the {{dev@}} mailing list that the FIP has been created, use the
> subject line {{[DISCUSS] FIP-0 Fineract Improvement Proposals}}, the body of
> the email should look something like {{Please discuss & subscribe here:
> https://github.com/apache/fineract-CN-repo/issues/5602}}
> # When writing the issue, fill in the sections as described above in “What
> should be included in a FIP?”.
> # A committer will initiate the discussion, and ensure that there’s enough
> time to analyze the proposal. Before accepting the FIP, a committer should
> call for a vote, requiring 3 votes and no vetoes from committers. Votes are
> timebox at 1 week, and conducted through email (with the subject [VOTE]).
> # Create a pull request implementing the FIP, and referencing the issue.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Closed] (FINCN-352) Fineract Improvement Proposals
[
https://issues.apache.org/jira/browse/FINCN-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrle Krantz closed FINCN-352.
--
Resolution: Fixed
There's no community consensus on a problem or a solution here.
> Fineract Improvement Proposals
> --
>
> Key: FINCN-352
> URL: https://issues.apache.org/jira/browse/FINCN-352
> Project: Fineract Cloud Native
> Issue Type: Improvement
>Reporter: Saransh Sharma
>Priority: Major
>
> Purpose
> The purpose of a Fineract CN Improvement Proposal (FIP) is to introduce any
> major change into Fineract CN. This is required in order to balance the need
> to support new features, uses cases , automation . Given the nature of the
> project that is micro services and its functional implications. To be able to
> bring changes in core libs and changes in the core services.
> What is considered as major change?
> Any of the following should be considered a major change:
> * Any major new feature, subsystem, or piece of functionality
> * Any change that removes the core lib
> * Design patterns changes that may take away the way project interact with
> respect to the services and db
> * Removal of services and core libs
> * Adding a new type and frameworks
> * Adding external service like automation and boilerplates
> * Architectural changes overhaul like moving service or merging service in
> single piece
> What should be included in the FIP
> * Motivation: describe the problem to be solved.
> * Proposed Change: describe the new thing you want to do. This may be fairly
> extensive and have large subsections of its own. Or it may be a few
> sentences, depending on the scope of the change.
> * New or Changed Public Interfaces: impact to any of the "compatibility
> commitments" described above. We want to call these out in particular so
> everyone thinks about them.
> * New dependencies: describe any third-party libraries that the feature will
> require, from PyPI or NPM. In particular, make sure their license is
> compatible with the [Apache License v2.0]
> ([https://www.apache.org/licenses/LICENSE-2.0]).
> * Migration Plan and Compatibility: if this feature requires additional
> support for seamless upgrades describe how that will work. In particular,
> it’s important to mention if:
> ** The feature requires a change in some way to core libs
> ** Some API level change
> ** Removing some lib or its generation
> ** The feature will coexist with similar functionality for some period of
> time, allowing for a deprecation period.
> * Rejected Alternatives: What are the other alternatives you considered and
> why are they worse? The goal of this section is to help people understand why
> this is the best solution now, and also to prevent churn in the future when
> old alternatives are reconsidered.
> Who should initiate FIP
> Anyone can initiate a FIP, but preferably someone with the intention of
> implementing it.
> Process
> # [Create an issue|https://github.com/apache/incubator-superset/issues] with
> the prefix “[FIP]” in the title. The issue will be tagged as “fip” by a
> committer, and the title will be updated with the current SIP number.
> # Notify the {{dev@}} mailing list that the FIP has been created, use the
> subject line {{[DISCUSS] FIP-0 Fineract Improvement Proposals}}, the body of
> the email should look something like {{Please discuss & subscribe here:
> https://github.com/apache/fineract-CN-repo/issues/5602}}
> # When writing the issue, fill in the sections as described above in “What
> should be included in a FIP?”.
> # A committer will initiate the discussion, and ensure that there’s enough
> time to analyze the proposal. Before accepting the FIP, a committer should
> call for a vote, requiring 3 votes and no vetoes from committers. Votes are
> timebox at 1 week, and conducted through email (with the subject [VOTE]).
> # Create a pull request implementing the FIP, and referencing the issue.
>
>
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (FINCN-12) clear IP for Fineract CN
[ https://issues.apache.org/jira/browse/FINCN-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17396493#comment-17396493 ] Myrle Krantz commented on FINCN-12: --- I don't know if this was ever completed. I'm also do not remember why I'm the assignee on this issue. Assuming the Fineract PMC intends to create a release that includes this code at some point, someone else should take this over, since I am no longer on the Fineract PMC and cannot act for it. That being said, IP clearance is entrusted to the incubator (also for graduated projects). The process for IP clearance is documented here: https://incubator.apache.org/ip-clearance/index.html > clear IP for Fineract CN > > > Key: FINCN-12 > URL: https://issues.apache.org/jira/browse/FINCN-12 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Blocker > > [https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/fineract-cn.xml] > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (FINCN-12) clear IP for Fineract CN
[ https://issues.apache.org/jira/browse/FINCN-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-12: - Assignee: (was: Myrle Krantz) > clear IP for Fineract CN > > > Key: FINCN-12 > URL: https://issues.apache.org/jira/browse/FINCN-12 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Myrle Krantz >Priority: Blocker > > [https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/fineract-cn.xml] > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (FINCN-13) clear IP for Fineract CN mobile
[ https://issues.apache.org/jira/browse/FINCN-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16879623#comment-16879623 ] Myrle Krantz commented on FINCN-13: --- Yes this is still relevant. On Sat, Jul 6, 2019 at 6:56 AM Awasum Yannick (JIRA) > clear IP for Fineract CN mobile > --- > > Key: FINCN-13 > URL: https://issues.apache.org/jira/browse/FINCN-13 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-mobile >Reporter: Myrle Krantz >Priority: Blocker > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINERACT-495) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/FINERACT-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz resolved FINERACT-495. --- Resolution: Fixed Assignee: Santosh Math (was: Shruthi M R) Santosh, in the future please delete previous releases when you create a new one. It's easier for the release manager to do, than for me to clean up after. > Please delete old releases from mirroring system > > > Key: FINERACT-495 > URL: https://issues.apache.org/jira/browse/FINERACT-495 > Project: Apache Fineract > Issue Type: Bug > Environment: https://dist.apache.org/repos/dist/release/fineract/ >Reporter: Sebb >Assignee: Santosh Math >Priority: Critical > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > It's not fair to expect the volunteer mirrors to carry old releases. > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-495) Please delete old releases from mirroring system
[ https://issues.apache.org/jira/browse/FINERACT-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16831173#comment-16831173 ] Myrle Krantz commented on FINERACT-495: --- Thanks for being persistent Sebb. I've given up on getting the release manager to finish this task and taken it on myself. It's cleaned up now. Best, Myrle > Please delete old releases from mirroring system > > > Key: FINERACT-495 > URL: https://issues.apache.org/jira/browse/FINERACT-495 > Project: Apache Fineract > Issue Type: Bug > Environment: https://dist.apache.org/repos/dist/release/fineract/ >Reporter: Sebb >Assignee: Shruthi M R >Priority: Critical > > To reduce the load on the ASF mirrors, projects are required to delete old > releases [1] > Please can you remove all non-current releases? > It's not fair to expect the volunteer mirrors to carry old releases. > Thanks! > [1] http://www.apache.org/dev/release.html#when-to-archive -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-702) Integrate SpotBugs and fail build if equals but not hashCode is implemented
[ https://issues.apache.org/jira/browse/FINERACT-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16791497#comment-16791497 ] Myrle Krantz commented on FINERACT-702: --- Would you be interested trying out the gradle upgrade? It is, as you can see, long overdue.. I've asked on the dev list if there are any objections. You could inform that discussion by trying it out and letting us know if you discover any problems. > Integrate SpotBugs and fail build if equals but not hashCode is implemented > --- > > Key: FINERACT-702 > URL: https://issues.apache.org/jira/browse/FINERACT-702 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger.ch >Priority: Major > Labels: starter > > This project should activate SpotBugs (the successor to FindBugs) and make it > fail the build for any violations to a at least a subset of rules which are > almost always guaranteed to be bugs. > For example, > https://spotbugs.readthedocs.io/en/stable/bugDescriptions.html#he-class-defines-equals-and-uses-object-hashcode-he-equals-use-hashcode > which would have caught what I manually spotted (but shouldn't have to) in > https://github.com/apache/fineract/pull/524. > FINERACT-402 has some history, but it's clearly not activated to enforce. > FINERACT-696 could then be built on top of this. > [~myrle] perhaps you know of any volunteer interested in doing this? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-702) Integrate SpotBugs and fail build if equals but not hashCode is implemented
[ https://issues.apache.org/jira/browse/FINERACT-702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz updated FINERACT-702: -- Labels: starter (was: ) > Integrate SpotBugs and fail build if equals but not hashCode is implemented > --- > > Key: FINERACT-702 > URL: https://issues.apache.org/jira/browse/FINERACT-702 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger.ch >Priority: Major > Labels: starter > > This project should activate SpotBugs (the successor to FindBugs) and make it > fail the build for any violations to a at least a subset of rules which are > almost always guaranteed to be bugs. > For example, > https://spotbugs.readthedocs.io/en/stable/bugDescriptions.html#he-class-defines-equals-and-uses-object-hashcode-he-equals-use-hashcode > which would have caught what I manually spotted (but shouldn't have to) in > https://github.com/apache/fineract/pull/524. > FINERACT-402 has some history, but it's clearly not activated to enforce. > FINERACT-696 could then be built on top of this. > [~myrle] perhaps you know of any volunteer interested in doing this? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINERACT-696) use SpotBugs and findbugs-slf4j to detect bad logging anti-patterns
[
https://issues.apache.org/jira/browse/FINERACT-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Myrle Krantz updated FINERACT-696:
--
Labels: starter (was: )
> use SpotBugs and findbugs-slf4j to detect bad logging anti-patterns
> ---
>
> Key: FINERACT-696
> URL: https://issues.apache.org/jira/browse/FINERACT-696
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Build
>Reporter: Michael Vorburger.ch
>Priority: Major
> Labels: starter
>
> While code reviewing [https://github.com/apache/fineract/pull/464], I came
> accross a {{catch}} & {{printStackTrace}}, which is of course wrong (it
> should instead be, correctly, logged, instead).
> In an ideal world, it would not take human code review to catch this, but
> just an automated build failure. This is possible using SpotBugs (not
> FindBugs anymore; SpotBugs is the new FindBugs, it's a fully compatible
> successor) and [https://github.com/KengoTODA/findbugs-slf4j/] (for this
> particular case [https://github.com/KengoTODA/findbugs-slf4j/issues/70], but
> using findbugs-slf4j for Fineract would have value even before that's
> implemented).
> [~myrle] you mentioned at FOSDEMO that you had hordes of volunteers just
> waiting to have issues to working on (I'm joking) - so I was wondering if
> perhaps you knew of anyone who would be willing to work on this one?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (FINCN-28) Adjust Permittables to make permission versioning possible
[ https://issues.apache.org/jira/browse/FINCN-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16788602#comment-16788602 ] Myrle Krantz commented on FINCN-28: --- Welcome [~walter211] ! Please subscribe to the dev list, and ask your questions there: dev-subscr...@fineract.apache.org > Adjust Permittables to make permission versioning possible > -- > > Key: FINCN-28 > URL: https://issues.apache.org/jira/browse/FINCN-28 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-anubis, fineract-cn-template >Reporter: Myrle Krantz >Assignee: Leopold Joy >Priority: Major > > When a service is provisioned, the provisioner requests all of the > permittable groups from the service and then saves them in identity. They > are saved under the service name and the service version. Groups cannot be > changed after they have been created because if they were, administrators > might find that users have permissions they were never intended to have. New > permittable groups can be added when new versions of a service are introduced. > Currently the service name and the service version are derived from a yaml > file. They could be changed via environment variables in the deployment of a > service. This is inconsistent with their close linking to the service code > and endpoints. If an administrator wished to change the service name they > would have to migrate all of the permissions for all of the users. > To rectify this situation, the service name and version should be made part > of every Permittable annotation on every endpoint. This will also make it > possible to version the permissions, and to place endpoints in multiple > permittable groups with multipile versions. > The new properties should be required. This means that all of the services > will have to be adjusted. Start with anubis (where the Permittable > annotation is defined), and then work on template to make sure the changes > work for a simple service. After that, all of the services will need to be > adjusted, and provisioning will need to be tested in the demo-server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-702) Integrate SpotBugs and fail build if equals but not hashCode is implemented
[ https://issues.apache.org/jira/browse/FINERACT-702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16770355#comment-16770355 ] Myrle Krantz commented on FINERACT-702: --- Perhaps @edcable knows of a volunteer who'd like to do this. > Integrate SpotBugs and fail build if equals but not hashCode is implemented > --- > > Key: FINERACT-702 > URL: https://issues.apache.org/jira/browse/FINERACT-702 > Project: Apache Fineract > Issue Type: Improvement >Reporter: Michael Vorburger.ch >Priority: Major > > This project should activate SpotBugs (the successor to FindBugs) and make it > fail the build for any violations to a at least a subset of rules which are > almost always guaranteed to be bugs. > For example, > https://spotbugs.readthedocs.io/en/stable/bugDescriptions.html#he-class-defines-equals-and-uses-object-hashcode-he-equals-use-hashcode > which would have caught what I manually spotted (but shouldn't have to) in > https://github.com/apache/fineract/pull/524. > FINERACT-402 has some history, but it's clearly not activated to enforce. > FINERACT-696 could then be built on top of this. > [~myrle] perhaps you know of any volunteer interested in doing this? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-558) Download page must link to ASF mirrors
[ https://issues.apache.org/jira/browse/FINERACT-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-558: - Assignee: Shruthi M R (was: Myrle Krantz) > Download page must link to ASF mirrors > -- > > Key: FINERACT-558 > URL: https://issues.apache.org/jira/browse/FINERACT-558 > Project: Apache Fineract > Issue Type: Bug > Environment: http://fineract.apache.org/ >Reporter: Sebb >Assignee: Shruthi M R >Priority: Critical > > Download pages must link to ASF mirror system. > They must not use dist.apache.org for anything. > See: > http://www.apache.org/dev/release-download-pages#links > Note the download page should also provide instructions for how to check > hashes and signatures. > The links to the hashes, signatures and KEYS file must be to the ASF server > and should use https. > However the links to the source and binary bundles must use the mirror system. > Likewise, announcement mails must not direct downloaders to the > dist.apache.org host. > Please fix the next announce email -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINCN-87) loan products interest must be given to two decimal points
[ https://issues.apache.org/jira/browse/FINCN-87?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz resolved FINCN-87. --- Resolution: Fixed > loan products interest must be given to two decimal points > -- > > Key: FINCN-87 > URL: https://issues.apache.org/jira/browse/FINCN-87 > Project: Fineract Cloud Native > Issue Type: Bug > Components: fineract-cn-fims-web-app >Reporter: Myrle Krantz >Assignee: Cabrel Kemfang >Priority: Major > > When creating a loan product, interest rate must be given to two decimal > points. There is no error message to explain why the input isn't accepted > before it is given to two decimal points. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-22) Fix TestSuite in teller
[ https://issues.apache.org/jira/browse/FINCN-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-22. - Resolution: Fixed > Fix TestSuite in teller > --- > > Key: FINCN-22 > URL: https://issues.apache.org/jira/browse/FINCN-22 > Project: Fineract Cloud Native > Issue Type: Bug > Components: fineract-cn-teller >Reporter: Myrle Krantz >Assignee: cabrel kemfang >Priority: Major > > As a programmer I want to be able to find out quickly if my changes have > caused existing functionality to break. The TestSuite class in the > component-test module of the fineract cn services is there to make one-click > testing of the services easy. > Currently when the TestSuite of fineract-cn-teller is run, only the first > Test class passes. The following test fails, and the remaining tests aren't > even included in the suite. These test pass when they are run individually > however. Apparently some part of the service spin up which should be part of > the base class is still in the child classes. This causes spin-up to fail > because the spin down is not completed by the time the next class starts. > Once this is fixed, you should also add the two missing test classes to the > test suite. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-22) Fix TestSuite in teller
[ https://issues.apache.org/jira/browse/FINCN-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-22: - Assignee: cabrel kemfang > Fix TestSuite in teller > --- > > Key: FINCN-22 > URL: https://issues.apache.org/jira/browse/FINCN-22 > Project: Fineract Cloud Native > Issue Type: Bug > Components: fineract-cn-teller >Reporter: Myrle Krantz >Assignee: cabrel kemfang >Priority: Major > > As a programmer I want to be able to find out quickly if my changes have > caused existing functionality to break. The TestSuite class in the > component-test module of the fineract cn services is there to make one-click > testing of the services easy. > Currently when the TestSuite of fineract-cn-teller is run, only the first > Test class passes. The following test fails, and the remaining tests aren't > even included in the suite. These test pass when they are run individually > however. Apparently some part of the service spin up which should be part of > the base class is still in the child classes. This causes spin-up to fail > because the spin down is not completed by the time the next class starts. > Once this is fixed, you should also add the two missing test classes to the > test suite. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-88) member loan ledger input help missing
[ https://issues.apache.org/jira/browse/FINCN-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-88. - Resolution: Fixed > member loan ledger input help missing > - > > Key: FINCN-88 > URL: https://issues.apache.org/jira/browse/FINCN-88 > Project: Fineract Cloud Native > Issue Type: Bug > Components: fineract-cn-fims-web-app >Reporter: Myrle Krantz >Assignee: cabrel kemfang >Priority: Major > > 1.) Go to loan products > 2.) Chose to create a new loan product > 3.) Go to ledger and account settings. > 4.) Try inputting cash fund account > 5.) Try inputting member loan ledger > Input help for cash fund account and meber loan ledger are different. In > cash fund account you can type the textual name of the account, but in member > loan ledger you can only type the number of the ledger. The name isn't > displayed except has a tooltip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-88) member loan ledger input help missing
Myrle Krantz created FINCN-88: - Summary: member loan ledger input help missing Key: FINCN-88 URL: https://issues.apache.org/jira/browse/FINCN-88 Project: Fineract Cloud Native Issue Type: Bug Components: fineract-cn-fims-web-app Reporter: Myrle Krantz 1.) Go to loan products 2.) Chose to create a new loan product 3.) Go to ledger and account settings. 4.) Try inputting cash fund account 5.) Try inputting member loan ledger Input help for cash fund account and meber loan ledger are different. In cash fund account you can type the textual name of the account, but in member loan ledger you can only type the number of the ledger. The name isn't displayed except has a tooltip. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-87) loan products interest must be given to two decimal points
Myrle Krantz created FINCN-87: - Summary: loan products interest must be given to two decimal points Key: FINCN-87 URL: https://issues.apache.org/jira/browse/FINCN-87 Project: Fineract Cloud Native Issue Type: Bug Components: fineract-cn-fims-web-app Reporter: Myrle Krantz When creating a loan product, interest rate must be given to two decimal points. There is no error message to explain why the input isn't accepted before it is given to two decimal points. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-35) Maintaining the Change log
[ https://issues.apache.org/jira/browse/FINCN-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467111#comment-16467111 ] Myrle Krantz commented on FINCN-35: --- At this point, Fineract CN has never been released by the Apache Fineract project, so a changelog is too early. When it comes time, please keep this data in Jira. I recommend inventing a ticket label to categorize tickets into those which should be contained in the changelog. The rest is just extracting the report appropriately based on the fixed version contained on the ticket. > Maintaining the Change log > -- > > Key: FINCN-35 > URL: https://issues.apache.org/jira/browse/FINCN-35 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-mobile >Reporter: Dilpreet Singh >Priority: Minor > > This is one of the important feature to tracking the change log because at > some instance we will some notes that will show what we have fixed or what we > going to. In this stage, this will help us to maintain project report. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-36) Project report
[ https://issues.apache.org/jira/browse/FINCN-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-36: - Assignee: Dilpreet Singh > Project report > -- > > Key: FINCN-36 > URL: https://issues.apache.org/jira/browse/FINCN-36 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-mobile >Reporter: Dilpreet Singh >Assignee: Dilpreet Singh >Priority: Minor > > This is most important part of the project because we are following the agile > process, so that will help us to decide, what's our next task -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINCN-38) Discussion for App logo
[ https://issues.apache.org/jira/browse/FINCN-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz updated FINCN-38: -- Component/s: fineract-cn-fims-web-app > Discussion for App logo > --- > > Key: FINCN-38 > URL: https://issues.apache.org/jira/browse/FINCN-38 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-fims-web-app, fineract-cn-mobile >Reporter: Dilpreet Singh >Priority: Minor > > As we know it is part of Fineract CN and not like a separate app that Mifos > controls although. > The project needs to discuss about an App logo to use. > We should use a similar or related logo for fims. (Fims currently contains > the kuelap logo, which looks kind of like an eye on the browser tab.) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-48) Update Parent UI if any new Loan, Customer, Deposit, Identification created.
[ https://issues.apache.org/jira/browse/FINCN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467089#comment-16467089 ] Myrle Krantz commented on FINCN-48: --- FINCN-47 likely results from the same difficulty. > Update Parent UI if any new Loan, Customer, Deposit, Identification created. > > > Key: FINCN-48 > URL: https://issues.apache.org/jira/browse/FINCN-48 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-mobile >Reporter: Dilpreet Singh >Priority: Minor > > Currently, we are updating the Customer, Loan Deposit and Identification > list, when ever we click on Plus fab button and So we should maintain a flag > that account created or not, If not then don't refresh list and If created > successfully then updated list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-48) Update Parent UI if any new Loan, Customer, Deposit, Identification created.
[ https://issues.apache.org/jira/browse/FINCN-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16467087#comment-16467087 ] Myrle Krantz commented on FINCN-48: --- This could actually be difficult in the mobile UI. The creation is asynchronous, so the mobile UI could only know when the creation is completed if it's listening in on the ActiveMQ. It can't do that though. Fixing this ticket might require the completion of the notifications framework for Fineract CN. > Update Parent UI if any new Loan, Customer, Deposit, Identification created. > > > Key: FINCN-48 > URL: https://issues.apache.org/jira/browse/FINCN-48 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-mobile >Reporter: Dilpreet Singh >Priority: Minor > > Currently, we are updating the Customer, Loan Deposit and Identification > list, when ever we click on Plus fab button and So we should maintain a flag > that account created or not, If not then don't refresh list and If created > successfully then updated list. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-53) Open login activity if refresh access token REST API Fails
[ https://issues.apache.org/jira/browse/FINCN-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-53: - Assignee: Dilpreet Singh > Open login activity if refresh access token REST API Fails > -- > > Key: FINCN-53 > URL: https://issues.apache.org/jira/browse/FINCN-53 > Project: Fineract Cloud Native > Issue Type: Improvement > Components: fineract-cn-mobile >Reporter: Dilpreet Singh >Assignee: Dilpreet Singh >Priority: Minor > > We are refreshing access token in splash activity and we have logic if > Refresh access token REST API fails with 403 exceptions then the user is > unauthorized. We need to make same logic in MifosBaseDataManager so if > refresh access token fails then open login activity. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-599) *.sha is deprecated, and must only be used for SHA-1
[ https://issues.apache.org/jira/browse/FINERACT-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINERACT-599. - Resolution: Fixed Indeed. Thank you for checking this again sebb. : o) > *.sha is deprecated, and must only be used for SHA-1 > > > Key: FINERACT-599 > URL: https://issues.apache.org/jira/browse/FINERACT-599 > Project: Apache Fineract > Issue Type: Bug >Reporter: Sebb >Assignee: Myrle Krantz >Priority: Minor > Labels: confirm > > The download page has links to *.sha files. > That's fine, but the contents appear to be SHA-512. > As such, the files must [1] be named *.sha512. > [1] http://www.apache.org/dev/release-distribution#sigs-and-sums -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINERACT-599) *.sha is deprecated, and must only be used for SHA-1
[ https://issues.apache.org/jira/browse/FINERACT-599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINERACT-599. - Resolution: Fixed Changed sha for most recent release (1.1.0), and updated release manager documentation to ensure that future release signatures are named correctly. > *.sha is deprecated, and must only be used for SHA-1 > > > Key: FINERACT-599 > URL: https://issues.apache.org/jira/browse/FINERACT-599 > Project: Apache Fineract > Issue Type: Bug >Reporter: Sebb >Assignee: Myrle Krantz >Priority: Minor > Labels: confirm > > The download page has links to *.sha files. > That's fine, but the contents appear to be SHA-512. > As such, the files must [1] be named *.sha512. > [1] http://www.apache.org/dev/release-distribution#sigs-and-sums -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-28) Adjust Permittables to make permission versioning possible
Myrle Krantz created FINCN-28: - Summary: Adjust Permittables to make permission versioning possible Key: FINCN-28 URL: https://issues.apache.org/jira/browse/FINCN-28 Project: Fineract Cloud Native Issue Type: Improvement Components: fineract-cn-anubis, fineract-cn-template Reporter: Myrle Krantz When a service is provisioned, the provisioner requests all of the permittable groups from the service and then saves them in identity. They are saved under the service name and the service version. Groups cannot be changed after they have been created because if they were, administrators might find that users have permissions they were never intended to have. New permittable groups can be added when new versions of a service are introduced. Currently the service name and the service version are derived from a yaml file. They could be changed via environment variables in the deployment of a service. This is inconsistent with their close linking to the service code and endpoints. If an administrator wished to change the service name they would have to migrate all of the permissions for all of the users. To rectify this situation, the service name and version should be made part of every Permittable annotation on every endpoint. This will also make it possible to version the permissions, and to place endpoints in multiple permittable groups with multipile versions. The new properties should be required. This means that all of the services will have to be adjusted. Start with anubis (where the Permittable annotation is defined), and then work on template to make sure the changes work for a simple service. After that, all of the services will need to be adjusted, and provisioning will need to be tested in the demo-server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINCN-27) Remove dependency to embedded MariaDB from component-test modules of all services.
[ https://issues.apache.org/jira/browse/FINCN-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz updated FINCN-27: -- Description: Fineract CN services currently depend on an embedded version of MariaDB for their component tests. This component is licensed as GPL, and therefore, needs to be replaced before we release. If we can't find a suitable replacement, an alternative would be to omit the component tests from our release. Why can't we have dependencies to GPL software? This sequence of events would be bad: 1.) We include GPL software in our release. 2.) Our code, including the GPL dependency is included in proprietary code of CompanyOmega 3.) Some judge somewhere decides that the "firewall" separating our code from the GPL isn't strong enough to call prevent the viral aspects of GPL from taking effect. 4.) CompanyOmega's proprietary code is now all open source and they go out of business. It's not a likely sequence, but because of the size of the negative outcome, we avoid it by not including GPL (or any other Category X software) in our releases. > Remove dependency to embedded MariaDB from component-test modules of all > services. > -- > > Key: FINCN-27 > URL: https://issues.apache.org/jira/browse/FINCN-27 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-template, fineract-cn-test >Reporter: Myrle Krantz >Priority: Major > > Fineract CN services currently depend on an embedded version of MariaDB for > their component tests. This component is licensed as GPL, and therefore, > needs to be replaced before we release. If we can't find a suitable > replacement, an alternative would be to omit the component tests from our > release. > Why can't we have dependencies to GPL software? This sequence of events would > be bad: > 1.) We include GPL software in our release. > 2.) Our code, including the GPL dependency is included in proprietary code of > CompanyOmega > 3.) Some judge somewhere decides that the "firewall" separating our code from > the GPL isn't strong enough to call prevent the viral aspects of GPL from > taking effect. > 4.) CompanyOmega's proprietary code is now all open source and they go out of > business. > It's not a likely sequence, but because of the size of the negative outcome, > we avoid it by not including GPL (or any other Category X software) in our > releases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-27) Remove dependency to embedded MariaDB from component-test modules of all services.
Myrle Krantz created FINCN-27: - Summary: Remove dependency to embedded MariaDB from component-test modules of all services. Key: FINCN-27 URL: https://issues.apache.org/jira/browse/FINCN-27 Project: Fineract Cloud Native Issue Type: Task Components: fineract-cn-template, fineract-cn-test Reporter: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINCN-2) Migrate ORM from Hibernate to OpenJPA
[ https://issues.apache.org/jira/browse/FINCN-2?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz updated FINCN-2: - Priority: Blocker (was: Major) > Migrate ORM from Hibernate to OpenJPA > - > > Key: FINCN-2 > URL: https://issues.apache.org/jira/browse/FINCN-2 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Awasum Yannick >Priority: Blocker > > Hibernate's license is not compliant with the Apache license. The goal of > this task is to remove all Hibernate related code and dependencies and > replace them with core Java and Apache OpenJPA equivalents so that full > compiance on the ORM side can be achieve. This is critical to getting > Fineract CN to fully become Apache Compliant. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-26) Replace MariaDB driver with drizzle as JDBC driver
Myrle Krantz created FINCN-26: - Summary: Replace MariaDB driver with drizzle as JDBC driver Key: FINCN-26 URL: https://issues.apache.org/jira/browse/FINCN-26 Project: Fineract Cloud Native Issue Type: Task Components: fineract-cn-mariadb Reporter: Myrle Krantz Fineract CN currently depends on 'org.mariadb.jdbc:mariadb-java-client:1.4.3' as our JDBC driver. It's for our connection to an SQL database, and can be used for MySQL as well as MariaDB. This component is licensed as LGPL, and therefore, needs to be replaced before we release. The current suggestion is to replace it with drizzle. Other suggestions are also welcome. Why can't we have dependencies to LGPL software? This sequence of events would be bad: 1.) We include LGPL software in our release. 2.) Our code, including the LGPL dependency is included in proprietary code of CompanyOmega 3.) Some judge somewhere decides that the "firewall" separating our code from the LGPL isn't strong enough to call prevent the viral aspects of LGPL from taking effect. 4.) CompanyOmega's proprietary code is now all open source and they go out of business. It's not a likely sequence, but because of the size of the negative outcome, we avoid it by not including LGPL (or any other Category X software) in our releases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-25) One process local deployment
Myrle Krantz created FINCN-25: - Summary: One process local deployment Key: FINCN-25 URL: https://issues.apache.org/jira/browse/FINCN-25 Project: Fineract Cloud Native Issue Type: Improvement Components: fineract-cn-demo-server Reporter: Myrle Krantz As a developer with a slightly older computer, I still want to be able to run all of the Fineract CN services so that I can develop on services with lots of dependencies or on the front end. Currently starting all of the services requires a pretty good computer; this excludes developers who can't afford it and it also makes production deployment of Fineract CN more expensive. It should be possible to create a one process version of the demo-server. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-16) Rename packages of fineract-cn-api and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-16?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-16. - Resolution: Fixed > Rename packages of fineract-cn-api and adjust dependent repositories > > > Key: FINCN-16 > URL: https://issues.apache.org/jira/browse/FINCN-16 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-15) Rename packages of fineract-cn-lang and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-15?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-15. - Resolution: Fixed > Rename packages of fineract-cn-lang and adjust dependent repositories > - > > Key: FINCN-15 > URL: https://issues.apache.org/jira/browse/FINCN-15 > Project: Fineract Cloud Native > Issue Type: Sub-task > Components: fineract-cn-lang >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-14) Rename packages of Fineract CN
[ https://issues.apache.org/jira/browse/FINCN-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-14. - Resolution: Fixed > Rename packages of Fineract CN > -- > > Key: FINCN-14 > URL: https://issues.apache.org/jira/browse/FINCN-14 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-20) Rename packages of fineract-cn-command and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-20. - Resolution: Fixed > Rename packages of fineract-cn-command and adjust dependent repositories > > > Key: FINCN-20 > URL: https://issues.apache.org/jira/browse/FINCN-20 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-18) Rename packages of fineract-cn-crypto and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-18. - Resolution: Fixed > Rename packages of fineract-cn-crypto and adjust dependent repositories > --- > > Key: FINCN-18 > URL: https://issues.apache.org/jira/browse/FINCN-18 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-21) Rename packages of fineract-cn-anubis and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-21. - Resolution: Fixed > Rename packages of fineract-cn-anubis and adjust dependent repositories > --- > > Key: FINCN-21 > URL: https://issues.apache.org/jira/browse/FINCN-21 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-19) Rename packages of fineract-cn-cassandra and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-19. - Resolution: Fixed > Rename packages of fineract-cn-cassandra and adjust dependent repositories > -- > > Key: FINCN-19 > URL: https://issues.apache.org/jira/browse/FINCN-19 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (FINCN-17) Rename packages of fineract-cn-async and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz closed FINCN-17. - Resolution: Fixed > Rename packages of fineract-cn-async and adjust dependent repositories > -- > > Key: FINCN-17 > URL: https://issues.apache.org/jira/browse/FINCN-17 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-21) Rename packages of fineract-cn-anubis and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-21: - Assignee: Myrle Krantz > Rename packages of fineract-cn-anubis and adjust dependent repositories > --- > > Key: FINCN-21 > URL: https://issues.apache.org/jira/browse/FINCN-21 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-23) Add a TestSuite to fineract-cn-reporting
Myrle Krantz created FINCN-23: - Summary: Add a TestSuite to fineract-cn-reporting Key: FINCN-23 URL: https://issues.apache.org/jira/browse/FINCN-23 Project: Fineract Cloud Native Issue Type: Task Components: fineract-cn-reporting Reporter: Myrle Krantz As a programmer I want to be able to find out quickly if my changes have caused existing functionality to break. The TestSuite class in the component-test module of the fineract cn services is there to make one-click testing of the services easy. For an example of a TestSuite see org.apache.fineract.cn.customer.TestSuite in fineract-cn-customer/component-test. There is no TestSuite available for fineract-cn-reporting currently. Please add one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-22) Fix TestSuite in teller
Myrle Krantz created FINCN-22: - Summary: Fix TestSuite in teller Key: FINCN-22 URL: https://issues.apache.org/jira/browse/FINCN-22 Project: Fineract Cloud Native Issue Type: Bug Components: fineract-cn-teller Reporter: Myrle Krantz As a programmer I want to be able to find out quickly if my changes have caused existing functionality to break. The TestSuite class in the component-test module of the fineract cn services is there to make one-click testing of the services easy. Currently when the TestSuite of fineract-cn-teller is run, only the first Test class passes. The following test fails, and the remaining tests aren't even included in the suite. These test pass when they are run individually however. Apparently some part of the service spin up which should be part of the base class is still in the child classes. This causes spin-up to fail because the spin down is not completed by the time the next class starts. Once this is fixed, you should also add the two missing test classes to the test suite. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-21) Rename packages of fineract-cn-anubis and adjust dependent repositories
Myrle Krantz created FINCN-21: - Summary: Rename packages of fineract-cn-anubis and adjust dependent repositories Key: FINCN-21 URL: https://issues.apache.org/jira/browse/FINCN-21 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-19) Rename packages of fineract-cn-cassandra and adjust dependent repositories
Myrle Krantz created FINCN-19: - Summary: Rename packages of fineract-cn-cassandra and adjust dependent repositories Key: FINCN-19 URL: https://issues.apache.org/jira/browse/FINCN-19 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-19) Rename packages of fineract-cn-cassandra and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-19: - Assignee: Myrle Krantz > Rename packages of fineract-cn-cassandra and adjust dependent repositories > -- > > Key: FINCN-19 > URL: https://issues.apache.org/jira/browse/FINCN-19 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-20) Rename packages of fineract-cn-command and adjust dependent repositories
Myrle Krantz created FINCN-20: - Summary: Rename packages of fineract-cn-command and adjust dependent repositories Key: FINCN-20 URL: https://issues.apache.org/jira/browse/FINCN-20 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Myrle Krantz Assignee: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-18) Rename packages of fineract-cn-crypto and adjust dependent repositories
Myrle Krantz created FINCN-18: - Summary: Rename packages of fineract-cn-crypto and adjust dependent repositories Key: FINCN-18 URL: https://issues.apache.org/jira/browse/FINCN-18 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-18) Rename packages of fineract-cn-crypto and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-18: - Assignee: Myrle Krantz > Rename packages of fineract-cn-crypto and adjust dependent repositories > --- > > Key: FINCN-18 > URL: https://issues.apache.org/jira/browse/FINCN-18 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-17) Rename packages of fineract-cn-async and adjust dependent repositories
[ https://issues.apache.org/jira/browse/FINCN-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-17: - Assignee: Myrle Krantz > Rename packages of fineract-cn-async and adjust dependent repositories > -- > > Key: FINCN-17 > URL: https://issues.apache.org/jira/browse/FINCN-17 > Project: Fineract Cloud Native > Issue Type: Sub-task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-17) Rename packages of fineract-cn-async and adjust dependent repositories
Myrle Krantz created FINCN-17: - Summary: Rename packages of fineract-cn-async and adjust dependent repositories Key: FINCN-17 URL: https://issues.apache.org/jira/browse/FINCN-17 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-16) Rename packages of fineract-cn-api and adjust dependent repositories
Myrle Krantz created FINCN-16: - Summary: Rename packages of fineract-cn-api and adjust dependent repositories Key: FINCN-16 URL: https://issues.apache.org/jira/browse/FINCN-16 Project: Fineract Cloud Native Issue Type: Sub-task Reporter: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-13) clear IP for Fineract CN mobile
[ https://issues.apache.org/jira/browse/FINCN-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-13: - Assignee: Myrle Krantz > clear IP for Fineract CN mobile > --- > > Key: FINCN-13 > URL: https://issues.apache.org/jira/browse/FINCN-13 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-mobile >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Blocker > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-12) clear IP for Fineract CN
[ https://issues.apache.org/jira/browse/FINCN-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-12: - Assignee: Myrle Krantz > clear IP for Fineract CN > > > Key: FINCN-12 > URL: https://issues.apache.org/jira/browse/FINCN-12 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Blocker > > [https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/fineract-cn.xml] > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINCN-13) clear IP for Fineract CN mobile
[ https://issues.apache.org/jira/browse/FINCN-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINCN-13: - Assignee: (was: Myrle Krantz) > clear IP for Fineract CN mobile > --- > > Key: FINCN-13 > URL: https://issues.apache.org/jira/browse/FINCN-13 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-mobile >Reporter: Myrle Krantz >Priority: Blocker > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-15) Rename packages of fineract-cn-lang and adjust dependent repositories
Myrle Krantz created FINCN-15: - Summary: Rename packages of fineract-cn-lang and adjust dependent repositories Key: FINCN-15 URL: https://issues.apache.org/jira/browse/FINCN-15 Project: Fineract Cloud Native Issue Type: Sub-task Components: fineract-cn-lang Reporter: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-14) Rename packages of Fineract CN
Myrle Krantz created FINCN-14: - Summary: Rename packages of Fineract CN Key: FINCN-14 URL: https://issues.apache.org/jira/browse/FINCN-14 Project: Fineract Cloud Native Issue Type: Task Reporter: Myrle Krantz -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-13) clear IP for Fineract CN mobile
Myrle Krantz created FINCN-13: - Summary: clear IP for Fineract CN mobile Key: FINCN-13 URL: https://issues.apache.org/jira/browse/FINCN-13 Project: Fineract Cloud Native Issue Type: Bug Components: fineract-cn-mobile Reporter: Myrle Krantz [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINCN-13) clear IP for Fineract CN mobile
[ https://issues.apache.org/jira/browse/FINCN-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz updated FINCN-13: -- Issue Type: Task (was: Bug) > clear IP for Fineract CN mobile > --- > > Key: FINCN-13 > URL: https://issues.apache.org/jira/browse/FINCN-13 > Project: Fineract Cloud Native > Issue Type: Task > Components: fineract-cn-mobile >Reporter: Myrle Krantz >Priority: Blocker > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-12) clear IP for Fineract CN
[ https://issues.apache.org/jira/browse/FINCN-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435148#comment-16435148 ] Myrle Krantz commented on FINCN-12: --- https://lists.apache.org/thread.html/6ca8580d5ff348b3b97a065c77d54c519c80d83dbd4ef49e4bf65f88@%3Cdev.fineract.apache.org%3E > clear IP for Fineract CN > > > Key: FINCN-12 > URL: https://issues.apache.org/jira/browse/FINCN-12 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Myrle Krantz >Priority: Blocker > > [https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/fineract-cn.xml] > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (FINCN-12) clear IP for Fineract CN
[ https://issues.apache.org/jira/browse/FINCN-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz updated FINCN-12: -- Issue Type: Task (was: Bug) > clear IP for Fineract CN > > > Key: FINCN-12 > URL: https://issues.apache.org/jira/browse/FINCN-12 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Myrle Krantz >Priority: Blocker > > [https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/fineract-cn.xml] > > [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (FINCN-12) clear IP for Fineract CN
Myrle Krantz created FINCN-12: - Summary: clear IP for Fineract CN Key: FINCN-12 URL: https://issues.apache.org/jira/browse/FINCN-12 Project: Fineract Cloud Native Issue Type: Bug Reporter: Myrle Krantz [https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/fineract-cn.xml] [https://incubator.apache.org/ip-clearance/index.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (FINCN-1) Import Fineract CN repositories from Mifos IO
[ https://issues.apache.org/jira/browse/FINCN-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz resolved FINCN-1. -- Resolution: Fixed Assignee: Myrle Krantz > Import Fineract CN repositories from Mifos IO > - > > Key: FINCN-1 > URL: https://issues.apache.org/jira/browse/FINCN-1 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Myrle Krantz >Assignee: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-1) Import Fineract CN repositories from Mifos IO
[ https://issues.apache.org/jira/browse/FINCN-1?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16435143#comment-16435143 ] Myrle Krantz commented on FINCN-1: -- Code is imported. Next step is getting it through IP-Clearance at the incubator. > Import Fineract CN repositories from Mifos IO > - > > Key: FINCN-1 > URL: https://issues.apache.org/jira/browse/FINCN-1 > Project: Fineract Cloud Native > Issue Type: Task >Reporter: Myrle Krantz >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-608) Share Dividends wrongly calculated
[ https://issues.apache.org/jira/browse/FINERACT-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-608: - Assignee: (was: Myrle Krantz) > Share Dividends wrongly calculated > -- > > Key: FINERACT-608 > URL: https://issues.apache.org/jira/browse/FINERACT-608 > Project: Apache Fineract > Issue Type: Bug > Components: Shares >Affects Versions: 1.0.0 >Reporter: Ippez Roberts >Priority: Critical > Fix For: 1.3.0 > > > I have seen some behavior with Share Account and Dividend. > I initiated a dividend payout of 100,000 to 4 clients with shares as below > > *Product>>Share Product>>Share Account (product name)>>Dividends* > ||Name||Dividend Period Start Date||Dividend Period End Date||Dividend > Amount||Status|| > |Share Account|01 January 2017|31 December 2017|100,000|Dividend Approved| > > |*Client Name*|*No. of Shares*| > |Asienzo|38 (approved) 1 pending approval| > |Mureo|40 (approved)| > |Drani|6 (approved)| > |Amatura|0| > |*TOTAL SHARES*|*84 (approved) 1 pending approval*| > > The distribution of dividend is as follow which to me is wrong. > > ||Client Name||Share Account||Dividend Amount||Status|| > |Asienzo Clara|21-1-0|29,260.01|Dividend Initiated| > |Mureo Stella|21-2-3|61,078.95|Dividend Initiated| > |Drani Joseph|21-3-1|8,192.8|Dividend Initiated| > |Amatura Women's Group|21-4-0|1,468.24|Dividend Initiated| > *Justification* > # Dividend per share = 100,000/84 = 1,190.48 ==> This is because there are > 84 approved shares, the 1 pending approval doesn't get dividend. > # Amatura Women's Group doesn't qualify for dividend because there is no > share purchased though they have opened a share account. > # To me the share distribution table should be as below:- > ||Client Name||Share Account||Dividend Amount||Status|| > |Asienzo Clara|21-1-0|45,238.24|Dividend Initiated| > |Mureo Stella|21-2-3|47,619.2|Dividend Initiated| > |Drani Joseph|21-3-1|7,142.88|Dividend Initiated| > |Amatura Women's Group|21-4-0|0|Dividend Initiated| > > Example, If we are calculating dividend for 2017, we get the total shares at > the organisation since inception of the organisation e.g if the organisation > started in 2003, we shall get total shares from 2003 upto 31st Dec 2017. Say > its 360 shares. > > Then if the approved dividend to be given to members is 720,000, we then get > how much each share will get i.e 720,000/360 = *2,000* > Now that we know each share gets 2,000, this will be the multiplying factor > for each members total share. > > Eg. > *Client Name Total Shares Dividend* > Client 1 1 > 2,000 > Client 2 5 > 10,000 > Client 3 10 > 20,000 > Client 4 0 0 > ... etc > > *TOTAL 360 > 720,000* > > Total amount given to clients should be equal to approved dividend. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-607) Need a bulk repayment functionality in MifosX
[ https://issues.apache.org/jira/browse/FINERACT-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-607: - Assignee: (was: Myrle Krantz) > Need a bulk repayment functionality in MifosX > - > > Key: FINERACT-607 > URL: https://issues.apache.org/jira/browse/FINERACT-607 > Project: Apache Fineract > Issue Type: Bug > Components: Groups, Loan > Environment: Apache Tomcat 7, MySQL 5,7.21, CentOS 7 >Reporter: Rituparna B >Priority: Major > > We use the MifosX Community App which runs on the Fineract Platform. > Requesting a new feature to enable the user enter group repayments in bulk, > instead of entering group-wise. This will save us a lot of valuable time. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-557) No obvious link to issue tracking system
[ https://issues.apache.org/jira/browse/FINERACT-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-557: - Assignee: (was: Myrle Krantz) > No obvious link to issue tracking system > > > Key: FINERACT-557 > URL: https://issues.apache.org/jira/browse/FINERACT-557 > Project: Apache Fineract > Issue Type: Bug >Reporter: Sebb >Priority: Major > > As the subject says: I could not find a link to the issue tracking system. > Since I am a long-time ASF committer, I knew it was probably in JIRA, but > that won't apply to the general reader of the website. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-609) Top loan is not working for Group loans
[ https://issues.apache.org/jira/browse/FINERACT-609?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-609: - Assignee: (was: Myrle Krantz) > Top loan is not working for Group loans > > > Key: FINERACT-609 > URL: https://issues.apache.org/jira/browse/FINERACT-609 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.0.0 >Reporter: Santosh Math >Priority: Major > Labels: gsoc, p1, volunteers > > # Create a loan product with top up enabled. > # Take a group loan and disburse it. > # Take another group loan application , Check 'Is top loan' and try to > select previous loan account. Previously created loan account is not > displaying. > Top up loan is working fine client level loan application. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-605) Bug when creating cashier in a teller without an end date
[ https://issues.apache.org/jira/browse/FINERACT-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-605: - Assignee: (was: Myrle Krantz) > Bug when creating cashier in a teller without an end date > - > > Key: FINERACT-605 > URL: https://issues.apache.org/jira/browse/FINERACT-605 > Project: Apache Fineract > Issue Type: Bug > Components: Organization >Affects Versions: 1.0.0 > Environment: Linux >Reporter: Nyota Macharia >Priority: Major > Labels: p1 > Fix For: 1.3.0 > > > When a User creates a teller without an end date, then proceeds to create a > cashier for this teller the following error appears > 05:34:05.816 [http-bio-443-exec-6] ERROR o.s.boot.context.web.ErrorPageFilter > - Forwarding to error page from request [/api/v1/tellers/1/cashiers] due to > exception [Partial cannot be null] > java.lang.IllegalArgumentException: Partial cannot be null > at org.joda.time.base.AbstractPartial.isAfter(AbstractPartial.java:351) > ~[joda-time-2.8.1.jar:2.8.1] > at > org.apache.fineract.organisation.teller.data.CashierTransactionDataValidator.validateCashierAllowedDateAndTime(CashierTransactionDataValidator.java:99) > ~[classes/:na] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-604) Support for MySQL 5.7
[ https://issues.apache.org/jira/browse/FINERACT-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-604: - Assignee: (was: Myrle Krantz) > Support for MySQL 5.7 > - > > Key: FINERACT-604 > URL: https://issues.apache.org/jira/browse/FINERACT-604 > Project: Apache Fineract > Issue Type: Improvement >Affects Versions: 1.0.0 > Environment: MySQL version 5.7.5 or higher >Reporter: Steve Conrad >Priority: Major > Labels: gsoc, p1 > Fix For: 1.2.0 > > > Provide support for MySQL 5.7. This includes all migrations scripts, services > code, and reports. The core issue is support for strict mode in MySQL > (ONLY_FULL_GROUP_BY enabled). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-606) Not able to delete groups which are assigned to center
[ https://issues.apache.org/jira/browse/FINERACT-606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-606: - Assignee: (was: Myrle Krantz) > Not able to delete groups which are assigned to center > -- > > Key: FINERACT-606 > URL: https://issues.apache.org/jira/browse/FINERACT-606 > Project: Apache Fineract > Issue Type: Bug > Components: Groups >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Major > Labels: p1 > Fix For: 1.2.0 > > > # Create a new center. > # Add existing group to the center using 'Manage groups' option under center. > # Again go to 'Manage Groups' and try to remove group from center. > >throwing validation: > field is required > error.msg.group.not.in.center - > > [https://staging.openmf.org/#/managegroupmembers/3] > > mifos/password -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-602) Unable to Submit loan application in demo server, going in infinite loop
[ https://issues.apache.org/jira/browse/FINERACT-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-602: - Assignee: (was: Myrle Krantz) > Unable to Submit loan application in demo server, going in infinite loop > > > Key: FINERACT-602 > URL: https://issues.apache.org/jira/browse/FINERACT-602 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Affects Versions: 1.1.0 >Reporter: Santosh Math >Priority: Blocker > Labels: p1 > Fix For: 1.2.0 > > > For the following client: > [https://demo.openmf.org/#/viewclient/4513] > Try to submit loan (clicking on 'New Loan) > Provide 'Submitted Date' and 'Expected Disbursement Date' as 11th February > 2018 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-610) Post Interest As On
[ https://issues.apache.org/jira/browse/FINERACT-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-610: - Assignee: (was: Myrle Krantz) > Post Interest As On > --- > > Key: FINERACT-610 > URL: https://issues.apache.org/jira/browse/FINERACT-610 > Project: Apache Fineract > Issue Type: Improvement > Components: Savings >Reporter: May Myint >Priority: Minor > Labels: saving > > Currently, Post Interest As On is only available when User is given ALL > FUNCTION permission. However, this is needed by many Users who should not be > given the ALL FUNCTION (loan officers etc). This function is used when a > client leaves the MFI and all their Savings are posted up to date and > withdrawn. It would be ideal to have a separate permission setting for this > function. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-8) Web UI for Microfinance Institutions Practicing Group Lending
[ https://issues.apache.org/jira/browse/FINCN-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391331#comment-16391331 ] Myrle Krantz commented on FINCN-8: -- How does this ticket relate to FINCN-3? > Web UI for Microfinance Institutions Practicing Group Lending > - > > Key: FINCN-8 > URL: https://issues.apache.org/jira/browse/FINCN-8 > Project: Fineract Cloud Native > Issue Type: New Feature >Reporter: Edward Cable >Priority: Major > Labels: gsoc2018 > > While the current Mifos X stack caters to one operational methodology and has > one distinct user interface and navigational flow, Fineract CN and it's > broader applicability enables many different operational workflows to be > supported and will have different flavors of the web UI. > For the brand new Apache Fineract CN architecture, the web UI for the first > use cases has been built out to support a teller-driven credit union > operational methodology. The user interface and navigational flows for such > an operational model is very different from that of a microfinance > institutinon with group and center-based operations whereby the loan officer > travels out to the customers rather than the customer goes to the branch > office. > The UI that will be built out for this project will be very similar to the UI > that was found in the current Gen 2 Mifos X web app as well as the original > Gen 1 web app with support for viewing group and center hierachies, having a > different drilldown navigational flow, etc. > A number of these UI elements will still need the requisite support on the > back-end. > Intern will implement the front-end UI screens for the Fineract CN web UI for > the following functionalities and use case: > * Center & Group Creation > * Center Summary and Details Page > * Group Summary and Details Page > * Group/Center Meeting Page > * Group, Center Listing View > * Drilldown navigation via Groups/Centers > * Collection sheet user interface > * Transferring clients between groups > * Group loan creation UI > * Group loan UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINCN-8) Web UI for Microfinance Institutions Practicing Group Lending
[ https://issues.apache.org/jira/browse/FINCN-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16391323#comment-16391323 ] Myrle Krantz commented on FINCN-8: -- Are the collection sheets paper, or UI? I'm guessing that since the loan officer is traveling to the customers, connectivity will be a problem. If that's true than an offline first approach is needed. Is this assumption correct? Can you provide (attach) examples of collections sheets currently in use? What does it mean for a client to be transferred between groups. What happens with their debt/savings? Can you detail what differentiates a group loan from a credit union loan? As far as the process goes? As far as the information required goes? > Web UI for Microfinance Institutions Practicing Group Lending > - > > Key: FINCN-8 > URL: https://issues.apache.org/jira/browse/FINCN-8 > Project: Fineract Cloud Native > Issue Type: New Feature >Reporter: Edward Cable >Priority: Major > Labels: gsoc2018 > > While the current Mifos X stack caters to one operational methodology and has > one distinct user interface and navigational flow, Fineract CN and it's > broader applicability enables many different operational workflows to be > supported and will have different flavors of the web UI. > For the brand new Apache Fineract CN architecture, the web UI for the first > use cases has been built out to support a teller-driven credit union > operational methodology. The user interface and navigational flows for such > an operational model is very different from that of a microfinance > institutinon with group and center-based operations whereby the loan officer > travels out to the customers rather than the customer goes to the branch > office. > The UI that will be built out for this project will be very similar to the UI > that was found in the current Gen 2 Mifos X web app as well as the original > Gen 1 web app with support for viewing group and center hierachies, having a > different drilldown navigational flow, etc. > A number of these UI elements will still need the requisite support on the > back-end. > Intern will implement the front-end UI screens for the Fineract CN web UI for > the following functionalities and use case: > * Center & Group Creation > * Center Summary and Details Page > * Group Summary and Details Page > * Group/Center Meeting Page > * Group, Center Listing View > * Drilldown navigation via Groups/Centers > * Collection sheet user interface > * Transferring clients between groups > * Group loan creation UI > * Group loan UI -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-557) No obvious link to issue tracking system
[ https://issues.apache.org/jira/browse/FINERACT-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-557: - Assignee: Myrle Krantz (was: Markus Geiss) > No obvious link to issue tracking system > > > Key: FINERACT-557 > URL: https://issues.apache.org/jira/browse/FINERACT-557 > Project: Apache Fineract > Issue Type: Bug >Reporter: Sebb >Assignee: Myrle Krantz >Priority: Major > > As the subject says: I could not find a link to the issue tracking system. > Since I am a long-time ASF committer, I knew it was probably in JIRA, but > that won't apply to the general reader of the website. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (FINERACT-558) Download page must link to ASF mirrors
[ https://issues.apache.org/jira/browse/FINERACT-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Myrle Krantz reassigned FINERACT-558: - Assignee: Myrle Krantz (was: Markus Geiss) > Download page must link to ASF mirrors > -- > > Key: FINERACT-558 > URL: https://issues.apache.org/jira/browse/FINERACT-558 > Project: Apache Fineract > Issue Type: Bug > Environment: http://fineract.apache.org/ >Reporter: Sebb >Assignee: Myrle Krantz >Priority: Critical > > Download pages must link to ASF mirror system. > They must not use dist.apache.org for anything. > See: > http://www.apache.org/dev/release-download-pages#links > Note the download page should also provide instructions for how to check > hashes and signatures. > The links to the hashes, signatures and KEYS file must be to the ASF server > and should use https. > However the links to the source and binary bundles must use the mirror system. > Likewise, announcement mails must not direct downloaders to the > dist.apache.org host. > Please fix the next announce email -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (FINERACT-517) "Recalculate Interest for Loans" scheduler job has no effect when partial payment is made with less amount on scheduled date.
[ https://issues.apache.org/jira/browse/FINERACT-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16169673#comment-16169673 ] Myrle Krantz commented on FINERACT-517: --- Test message (testing mailing list integration) > "Recalculate Interest for Loans" scheduler job has no effect when partial > payment is made with less amount on scheduled date. > - > > Key: FINERACT-517 > URL: https://issues.apache.org/jira/browse/FINERACT-517 > Project: Apache Fineract > Issue Type: Bug > Components: Loan >Reporter: Santosh Math >Assignee: Santosh Math > Labels: p1 > > When there is less repayment is made(Ex; 500 in stead of 1000), it is needed > to run the scheduler job but running this scheduler job has no effect and > interest is not getting recalculated . > 1. Create a loan product (Monthly repayment) with Interest Recalculation > enabled. (Reduced EMI Amount, no compounding is required) > 2. Disburse loan on January 1, 2017 whose first repayment date will be 01 > February 2017. > 3. Consider repayment amount is 800, but you make repayment only 400 on 01 > February 2017. > 4. Run Scheduler job "Recalculate Interest for Loans' > >When you come back to the loan account, you see the same repayment schedule > >before running the scheduler job. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
