[
https://issues.apache.org/jira/browse/FINERACT-389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15963335#comment-15963335
]
Thisura commented on FINERACT-389:
----------------------------------
In the above PR https://github.com/openMF/community-app/pull/2157 the fix will
work only in the community-app.
However as discussed in the thread "Does the changes in apache fineract
platform necessary to fix FINERACT issues", it is suggested to implement these
kinds of changes in the backend, to decouple the front-end.
New PR sent at https://github.com/apache/incubator-fineract/pull/330 to
incorporate this into the backend.
> Arrange the accounts that fall under one account type in order of their GL
> codes
> --------------------------------------------------------------------------------
>
> Key: FINERACT-389
> URL: https://issues.apache.org/jira/browse/FINERACT-389
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Accounting
> Reporter: Santosh Math
> Assignee: Markus Geiss
> Priority: Minor
> Labels: p2
>
> Reported by Mexina Daniel at https://mifosforge.jira.com/browse/MIFOSX-2825
> Original Description:
> Accounts in chart of accounts are arranged by their account type but those
> accounts in the specific account type are randomly arranged.
> I was recommending for the accounts in the same account type to be arranged
> by their GL code. Since the relating accounts will be under one header and so
> their GL codes will be following each other and bring presentable
> arrangement. (accounts in the same header, their GL codes should have
> relation)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
