[jira] [Commented] (FINERACT-378) Not able to link savings account in Bulk JLG Loan application page

[Brian C Cooke (JIRA)]

[ 
https://issues.apache.org/jira/browse/FINERACT-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15843811#comment-15843811
 ] 

Brian C Cooke commented on FINERACT-378:


linked bug in mifosx jira is closed, this should be closed as well

> Not able to link savings account in Bulk JLG Loan application page
> --
>
> Key: FINERACT-378
> URL: https://issues.apache.org/jira/browse/FINERACT-378
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
> Attachments: 11.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1570
> And also: https://github.com/openMF/community-app/issues/1681
> Original Description:
> Create a Center with meeting date, create Group under that Center and attach 
> 3 Clients under that Group, Create a Loan product
> Click on the Center -> Groups -> Select a particular Group ->Click on Bulk 
> JLG Loan Application button -> Select the Loan product - In which Link 
> savings account drop-down is not displaying.
> If any loan charges due is need to be collected from Linked savings account 
> then it is not possible in this case. Check  the screenshot.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Please help evaluation Fineract's readiness for graduation

[Jim Jagielski]

Makes sense.
> On Jan 25, 2017, at 10:52 PM, Shaik Nazeer 
>  wrote:
> 
> Instead of modifying Fineract website on every Fineract releases, can we link 
> required details to Fineract wiki pages? 
> For example latest release details can be found at 
> https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders
> 
> Thanks,
> Nazeer
> -Original Message-
> From: Markus Geiß [mailto:mge...@mifos.org] 
> Sent: 26 January 2017 01:55
> To: Ed Cable
> Cc: dev (dev@fineract.incubator.apache.org)
> Subject: Re: Please help evaluation Fineract's readiness for graduation
> 
> Hey Ed,
> 
> the Apache Fineract website is a github repo you'll find at Apache's github 
> mirror.
> 
> Simply fork it, create a new branch, do the needed changes and send a PR.
> 
> Best wishes,
> 
> Markus Geiss
> Chief Architect
> RɅĐɅЯ, The Mifos Initiative
> 
> On Jan 24, 2017 15:58, "Ed Cable"  wrote:
> 
>> Markus,
>> 
>> Nazeer is continuing to work on addressing the areas of concern 
>> related to QU10, QU40, and RE50.
>> 
>> Could you provide me access to the Apache Fineract website to address 
>> CO10 and then for CS10 do we want that on the Apache Fineract website 
>> or the wiki?
>> 
>> Thanks,
>> 
>> Ed
>> 
>> On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski  wrote:
>> 
>>> Agreed.
>>> 
 On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik 
>>> wrote:
 
 On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable  wrote:
> Could our Apache Fineract mentors please provide some guidance on 
> a
>>> couple
> of the areas we need to improve upon:
> 
> QU10 "*The project is open and honest about the quality of its code.
> Various levels of quality and maturity for various modules are 
> natural
>>> and
> acceptable as long as they are clearly communicated." -*
> 
> Do you have any other projects you could point to that have strong 
> transparent measures of quality and maturity clearly available We 
> want
>>> to
> follow best practices and adopt similar to display at 
> http://fineract.incubator.apache.org
 
 Regular deployment of tools like Findbugs is a good indication that 
 you
>>> take
 this requirement seriously.
 
> *QU30: The project provides a well-documented channel to report
>>> security
> issues, along with a documented way of responding to them.*
> 
> Currently we just link to: http://www.apache.org/security/ Are we
>>> able to
> do as other projects at 
> http://www.apache.org/security/projects.html
>>> or is
> a private channel not something we can set up till we're out of 
> incubation.  If we can move forwarde, I'd suggest we have a 
> security
>>> page
> on our site, document and fix known vulnerabilities and then 
> provide
>>> clear
> instruction on reporting vulnerabilities to a private channel like 
> secur...@fineract.incubator..apache.org
 
 This is less about security@fineract vs.
>>> http://www.apache.org/security/
 and more about the community being ready for when the first 0 day 
 hits either of those. Being ready is a combination of tribal 
 knowledge, wiki recommendations and a release policy that would 
 allow you to patch at a drop of a hat.
 
 Thanks,
 Roman.
>>> 
>>> 
>> 
>> 
>> --
>> *Ed Cable*
>> Director of Community Programs, Mifos Initiative edca...@mifos.org | 
>> Skype: edcable | Mobile: +1.484.477.8649 <(484)%20477-8649>
>> 
>> *Collectively Creating a World of 3 Billion Maries | *http://mifos.org 
>>   
>> 
>> 
> 

Re: Charts of Accounts

[Sampath Kumar G]

Hi Mexina,

All the GL accounts are ordered based on the 'Account Type'.

Thanks and regards,
Sampath


​
*Conflux Technologies Pvt Ltd  *

#304, 2nd Floor, 7th Main Road

HRBR Layout 1st Block

Bengaluru, Karnataka, 560043 INDIA


Disclaimer: The information contained in this e-mail message and any
files/attachment transmitted with it is confidential and for the sole use
of the intended recipient(s) or entity identified. If you are not the
intended recipient, please email: supp...@confluxtechnologies.com and
destroy/delete all copies and attachment thereto along with the original
message. Any unauthorised review, use, disclosure, dissemination,
forwarding, printing or copying of this email or any action taken in
reliance on this e-mail is strictly prohibited and is unlawful. The
recipient acknowledges that Conflux Technologies Private Limited or its
subsidiaries and associated companies are unable to exercise control or
ensure or guarantee the integrity of/over the contents of the information
contained in e-mail transmissions. Before opening any attachments, please
check.

On Fri, Jan 27, 2017 at 1:51 PM, Mexina Daniel  wrote:

> Hi Devs
>
> I want to know what is the logic of the arrangement of list of chart of
> account in Mifos?
> I don't see them arranged in alphabetical order or even in GL codes.
>
> Thanks in advance
>
> --
> Mexina M Daniel
> Lead Software Developer
> Research & Development
>
> Tel:+255 222 618 511 | Mob: +255 712 110 791
>
> Singo Africa Limited
> Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es Salaam
>
> singo.co.tz
>
> Lets grow together
>
>

Re: Please help evaluation Fineract's readiness for graduation

[Myrle Krantz]

Hey Ed,

Isn't that what Jira is for?  Wouldn't it be enough to just tag the release
version when a ticket is resolved?

Greets,
Myrle



*Myrle Krantz*
Solutions Architect
RɅĐɅЯ, The Mifos Initiative
mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
  


On Thu, Jan 26, 2017 at 8:01 PM, Ed Cable  wrote:

> To address Sendoro's comment, could we maintain the changelog (
> https://github.com/apache/incubator-fineract/blob/develop/CHANGELOG.md)
>
> just as we do the Mifos X changelog
>
>  https://github.com/openMF/incubator-fineract/blob/
> master/MIFOS-CHANGELOG.md
>
> whereby from the changelog you can immediately see history of changes and
> do as Sendoro would like and quickly decide whether to upgrade or not.
>
> Ed
>
> On Thu, Jan 26, 2017 at 10:58 AM, Ed Cable  wrote:
>
> > Nazeer,
> >
> > We do need to link to the latest download which in this case is 0.6.0
> from
> > https://dist.apache.org/repos/dist/release/incubator/fineract/
> >
> > Markus - is there a way in which to dynanmically link to the latest
> > release or do we always have to manually update.
> >
> >
> > On Wed, Jan 25, 2017 at 7:52 PM, Shaik Nazeer  > confluxtechnologies.com> wrote:
> >
> >> Instead of modifying Fineract website on every Fineract releases, can we
> >> link required details to Fineract wiki pages?
> >> For example latest release details can be found at
> >> https://cwiki.apache.org/confluence/display/FINERACT/Release+Folders
> >>
> >> Thanks,
> >> Nazeer
> >> -Original Message-
> >> From: Markus Geiß [mailto:mge...@mifos.org]
> >> Sent: 26 January 2017 01:55
> >> To: Ed Cable
> >> Cc: dev (dev@fineract.incubator.apache.org)
> >> Subject: Re: Please help evaluation Fineract's readiness for graduation
> >>
> >> Hey Ed,
> >>
> >> the Apache Fineract website is a github repo you'll find at Apache's
> >> github mirror.
> >>
> >> Simply fork it, create a new branch, do the needed changes and send a
> PR.
> >>
> >> Best wishes,
> >>
> >> Markus Geiss
> >> Chief Architect
> >> RɅĐɅЯ, The Mifos Initiative
> >>
> >> On Jan 24, 2017 15:58, "Ed Cable"  wrote:
> >>
> >> > Markus,
> >> >
> >> > Nazeer is continuing to work on addressing the areas of concern
> >> > related to QU10, QU40, and RE50.
> >> >
> >> > Could you provide me access to the Apache Fineract website to address
> >> > CO10 and then for CS10 do we want that on the Apache Fineract website
> >> > or the wiki?
> >> >
> >> > Thanks,
> >> >
> >> > Ed
> >> >
> >> > On Tue, Jan 10, 2017 at 5:48 AM, Jim Jagielski 
> wrote:
> >> >
> >> >> Agreed.
> >> >>
> >> >> > On Jan 6, 2017, at 8:41 PM, Roman Shaposhnik  >
> >> >> wrote:
> >> >> >
> >> >> > On Fri, Jan 6, 2017 at 4:24 PM, Ed Cable 
> wrote:
> >> >> >> Could our Apache Fineract mentors please provide some guidance on
> >> >> >> a
> >> >> couple
> >> >> >> of the areas we need to improve upon:
> >> >> >>
> >> >> >> QU10 "*The project is open and honest about the quality of its
> code.
> >> >> >> Various levels of quality and maturity for various modules are
> >> >> >> natural
> >> >> and
> >> >> >> acceptable as long as they are clearly communicated." -*
> >> >> >>
> >> >> >> Do you have any other projects you could point to that have strong
> >> >> >> transparent measures of quality and maturity clearly available We
> >> >> >> want
> >> >> to
> >> >> >> follow best practices and adopt similar to display at
> >> >> >> http://fineract.incubator.apache.org
> >> >> >
> >> >> > Regular deployment of tools like Findbugs is a good indication that
> >> >> > you
> >> >> take
> >> >> > this requirement seriously.
> >> >> >
> >> >> >> *QU30: The project provides a well-documented channel to report
> >> >> security
> >> >> >> issues, along with a documented way of responding to them.*
> >> >> >>
> >> >> >> Currently we just link to: http://www.apache.org/security/ Are we
> >> >> able to
> >> >> >> do as other projects at
> >> >> >> http://www.apache.org/security/projects.html
> >> >> or is
> >> >> >> a private channel not something we can set up till we're out of
> >> >> >> incubation.  If we can move forwarde, I'd suggest we have a
> >> >> >> security
> >> >> page
> >> >> >> on our site, document and fix known vulnerabilities and then
> >> >> >> provide
> >> >> clear
> >> >> >> instruction on reporting vulnerabilities to a private channel like
> >> >> >> secur...@fineract.incubator..apache.org
> >> >> >
> >> >> > This is less about security@fineract vs.
> >> >> http://www.apache.org/security/
> >> >> > and more about the community being ready for when the first 0 day
> >> >> > hits either of those. Being ready is a combination of tribal
> >> >> > knowledge, wiki recommendations and a release policy that would
> >> >> > allow you to patch at a drop of a hat.
> >> >> >
> >> >> > Thanks,
> >> >> > Roman.
> >> >>
> >> >>
> >> >

Charts of Accounts

[Mexina Daniel]

Hi Devs

I want to know what is the logic of the arrangement of list of chart of 
account in Mifos?

I don't see them arranged in alphabetical order or even in GL codes.

Thanks in advance

--
Mexina M Daniel
Lead Software Developer
Research & Development

Tel:+255 222 618 511 | Mob: +255 712 110 791

Singo Africa Limited
Block G,Mbezi Beach B| 7 Nakawale Road| P.O.Box 78908| 14121 Dar es Salaam

singo.co.tz

Lets grow together