[
https://issues.apache.org/jira/browse/FINERACT-1031?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17135235#comment-17135235
]
bharath gowda commented on FINERACT-1031:
-----------------------------------------
[~vorburger] I was following an email thread about this issue, there were no
conclusions or resolutions discussed except similar questions from your side on
that thread.
Since this issue was critical and affecting the accounting reports too, I
opened the original ticket FINERACT-645 initially to *Re-open* the issue,
however since there was no option to do so... I had to create a new Ticket. Did
you try reopening the issue?.. is the option available only for a particular
user group? - (check the screenshots where there is no option displaying for
reopening).
How other users should deal with this Kind of scenarios who doesn't have a
re-open option? The easiest option available is to create a new ticket by
cloning the existing one.
My intention was only to get the issue fixed and the only option available on
the Ticket-645 was to clone. again clone happened with one button, did not
provide an option to modify any fields in the cloning process. hence the fields
like 'fix version', 'assignee', 'Headings' were inherited from the original
ticket. and 'CLONE' label in heading was auto-added by the system. and it
simply means that this is a new ticket which is a CLONE/SIMILAR to a previous
ticket. other than this type of scenario let me know where else we can use the
CLONE option which is available?
> I tried to change the assignee but I don't have the permission for. Please
> change the Assignee if you can, I don't think [~Shruthi M R] is contributing
> any more to the Fineract(we were ex-colleagues before)
> I have changed the fixed version to only 1.4. again now. 1.2 was inherited
> from Original ticket, I did not notice at that time.
> Heading label having 'CLONE' - I do not see any harm as in this scenario it
> seemed valid to me, you can change it if you can think it gives a different
> perspective to the ticket and share it with us to so that we can avoid such
> scenarios in future.
!image-2020-06-14-22-19-54-702.png!
> CLONE - Advanced accounting for fees not working
> -------------------------------------------------
>
> Key: FINERACT-1031
> URL: https://issues.apache.org/jira/browse/FINERACT-1031
> Project: Apache Fineract
> Issue Type: Bug
> Components: Accounting, Loan
> Affects Versions: 1.1.0
> Reporter: bharath gowda
> Assignee: Shruthi M R
> Priority: Major
> Labels: gsoc, p1
> Fix For: 1.2.0, 1.4.0
>
> Attachments: 1.png, 2.png, 3.png, image-2020-06-14-22-19-54-702.png
>
>
> //Resurfaced Issue //
> Deepak's description in mailing list:
>
> I was to map the different accounting GLs for different Fees. I mapped the
> GLs to the respective fees. PFA the screenshot. But still in accounting, the
> entry has gone to the single GL
> https: demo.openmf.org
> username: mifos
> password: password
>
> Loan ID: depk000002980
> Product Name: deepak
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
