Hello Olaitan,

 

It seems like you and several others in your organization (Abdul-Quadri
Dauda and Owoeye Sunday Laurence) are working on deploying Mifos and as
you work with the current version of the code, you are encountering some
issues along the way.  I'm guessing you are all from the same
organization since you all have the same domain name on your email
address.  Feel free to correct me if I am wrong on that assumption.

 

You may have noticed in my recent email to the developer list in
response to Abdul-Quadri's question about session time-out errors, I
provided some information about how to enter bug reports into the Mifos
issue tracker.  These guidelines are helpful for entering bug reports
into the issue tracker but also a helpful template for how to provide
information when emailing the developer list with potential issues you
are encountering.  If you can provide information in this format, I
think we will be in a much better position to answer your questions.

 

Please see the attached email (it is not showing up in the archives yet)
for the guidelines I recently provided about how to report issues to the
Mifos community.

 

If you have any questions about this process, feel free to let us know
and we will be happy to assist you further.

 

Thanks,

 

Aliya

 

________________________________

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
olaitan kazeem
Sent: Tuesday, March 04, 2008 4:51 PM
To: [email protected];
[EMAIL PROTECTED]
Subject: [Mifos-functional] PROBLEM WITH THE DATE NOT APPEARING FOR
MYCLIENTS ON THE TRANSACTIOIN HISTORY PAGE ON MIFOS VERSION 1.1

 


hello,

Please am having a problem on my clients transaction history page not
displaying the date but the date column is there and nothing is
appearing under it whenever u apply payments.

but the date of transaction is displayed under the date posted column,
so  please help me look into the date for appropriate control over it

i will be very grateful to receive an helpful message concerning this.

Thanks i will be expecting your reply.  

--- Begin Message ---
> If you still desire further customization of the error page, please
file
> a feature request in the issue tracker.

As Adam mentions, if any of the issues you are facing with the current
version of the code (latest version of the trunk in SVN) are not already
reported in the issue tracker, it is best if you can put in a detailed
description of the steps are you taking that result in the issue and log
this in a bug in the issue tracker.  This will ensure that your issue is
reviewed and considered for being fixed in v1.1 or in a later release of
Mifos.  Otherwise, there is no way to ensure that we are aware of your
issue and can plan to fix it in the future.

In general, you want to include detailed, step by step instructions for
how someone trying to replicate your error can do so.  For example, in
this case, you would want to write a bug which included:

*  Software stack you are using (Operating system/Java Version/MySQL
Version/App Server and Version)
*  Revision number of the WAR file you are using
*  Information about the DB you have loaded when reproducing the bug.
In general, you want to include the steps to reproduce it from a clean
DB installation, whenever possible.
*  Clear reproduction steps with the observed outcome and expected
outcome as well as attachments of any error messages, log files, or
screen shots to demonstrate the issue.  For example:

        REPRO
        =====
        1.  Log into Mifos
        2.  Click on Admin tab
        3.  Click on link x
        4.  Wait x number of minutes
        5.  Click on Clients and Accounts tab

        OBSERVED
        ========
        HTTP 500 error (and attach full details of the error)

        EXPECTED
        ========
        No error.  User should be able to navigate to Clients and
Accounts tab    (or user should be redirected to log in again since
session timeout         has been reached)

For more information about how to log issues in the issue tracker,
please see this page:

http://mifos.org/developers/testing/bug-entry-guidelines 

If you have any other questions about how to enter an issue into the
issue tracker, please feel free to email the list and we can answer your
questions.

Thanks,

Aliya



-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/


--- End Message ---
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

Reply via email to