[
https://issues.apache.org/jira/browse/FINERACT-536?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712682#comment-16712682
]
Shruthi M R commented on FINERACT-536:
---------------------------------------
[~mexina] can you elaborate on the 'source codes to change the category of the
report'.
And for the Pentaho are you saying the design of the Pentaho which is created
using Pentaho designer? If yes, then yes if you want to make changes to the
existing Pentaho report, it needs to deployed on the server and then user can
user it.
And I will give the migration script for the existing records.
> Report categories are inconsistent and causing reports to go missing in the
> drop-down
> -------------------------------------------------------------------------------------
>
> Key: FINERACT-536
> URL: https://issues.apache.org/jira/browse/FINERACT-536
> Project: Apache Fineract
> Issue Type: Improvement
> Components: System
> Affects Versions: 1.0.0
> Reporter: thynn win
> Assignee: Shruthi M R
> Priority: Minor
> Labels: gci, gsoc, p1
> Fix For: 1.3.0
>
> Attachments: Untitled.gif
>
>
> Currently in Mifos, if you go to Reports menu and use the drop down to see
> "Clients" or "Loans", we notice that some reports are not showing up in the
> proper list.
> For instance, if you pick Reports>Clients , some client reports such as
> "Client Listing" will not show up. This is because the category is 'Clients'
> while the expected category value for "Clients" drop down is "Client".
> The same issue presents for other category such as Loans. In this case, some
> loan reports are created with category "Loan" not "Loans" and then they are
> not showing up. It's confusing to end users.
> To solve this, review all the report categories and make sure they are
> consistent with the expected value from the drop down (be it Client or
> Loans).
> Acceptance criteria:
> All the report categories are cleaned up and consistent and they should all
> show up under right drop-down.
> The end result is a sql script for the next release that fixes it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
