[
http://mifosforge.jira.com/browse/MIFOS-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Van Mittal-Henkle reassigned MIFOS-3633:
----------------------------------------
Assignee: Kay Chau (was: Van Mittal-Henkle)
Seems like we have a version number in place that is displayed in reports now.
Kay can you confirm that this satisfies this requirement and close this if it
does?
> 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: jbrewster
> Assignee: Kay Chau
> Fix For: Mifos Backlog
>
>
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
