[ 
http://mifosforge.jira.com/browse/MIFOS-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

keithwoodlock updated MIFOS-3633:
---------------------------------

    Fix Version/s:     (was: Mifos Backlog)
                   Unscheduled

> Add versioning info to new reports
> ----------------------------------
>
>                 Key: MIFOS-3633
>                 URL: http://mifosforge.jira.com/browse/MIFOS-3633
>             Project: mifos
>          Issue Type: Improvement
>          Components: Reports Module
>    Affects Versions: Release 2.0.0
>            Reporter: Jeff Brewster
>            Assignee: Kay Chau
>             Fix For: Unscheduled
>
>
> As we build new Pentaho standard reports, we should identify a simple process 
> for adding versions to the reports.  This version information would help the 
> release team (QA) and administrators be sure the right copy of reports are 
> being tested and deployed.
> Ideally, the version info would be accessible from the Pentaho tools but not 
> visible on viewable/printable reports.  

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
What Every C/C++ and Fortran developer Should Know!
Read this article and learn how Intel has extended the reach of its 
next-generation tools to help Windows* and Linux* C/C++ and Fortran 
developers boost performance applications - including clusters. 
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues

Reply via email to