Redmine Timesheets Application - Redmine Pluginshttps://www.redmine.org/2015-03-25T15:51:30ZRedmine
Redmine 1.5.3https://www.redmine.org/plugins/redmine_app_timesheets#1.5.32015-03-25T15:51:30ZMassimo Rossello
<p>Compatibility with Redmine 3.0 / Rails 4</p> 1.4.6https://www.redmine.org/plugins/redmine_app_timesheets#1.5.32014-12-04T20:23:36ZMassimo Rossello
<p>Local orders (those defined as Versions in projects) do not need to be shared any more. A custom field defines if a Version is also an Order, instead.</p> 1.3.16https://www.redmine.org/plugins/redmine_app_timesheets#1.5.32014-06-04T07:56:06ZMassimo Rossello
<p>Dependency from redmine_watcher_groups has been removed.<br />Usage of hidden issues in the backing project has been removed.</p>
<p>WARNING: database migration is not reversible. Please save your db before upgrading.</p> 1.3.1https://www.redmine.org/plugins/redmine_app_timesheets#1.5.32014-01-27T12:45:25ZMassimo Rossello
<a name="13"></a>
<h3 >1.3<a href="#13" class="wiki-anchor">¶</a></h3>
<p>View/Edit permissions on global Orders can be given through the Order config interface on a per-Order granularity. Redmine administrators and Orders administrators (those who can access the interface) always have Edit permission on every Order.</p>
<p>Above interface removes the need to assign role permissions over the timelogs to members into the backing project, and therefore completely removes the need to enable the Issue Tracking module in it.</p>
<p>Fixed several security issues.</p>
<p>WARNING: if you migrate from version 1.2 or below you will have to redefine any view/edit permissions over Orders that you may have assigned through roles into the backing project.</p>
<a name="12"></a>
<h3 >1.2<a href="#12" class="wiki-anchor">¶</a></h3>
<p>Activities logged on the timesheet is disjoint from activity logged in the project as well. Therefore, timesheets may define a lighter, or conversely a more rafinate, set of activities which do not impact project management.</p>
<p>Added Order Activity criteria for spent time.</p>
<p>Significative changes in database, may bring instability.</p>
<a name="11"></a>
<h3 >1.1<a href="#11" class="wiki-anchor">¶</a></h3>
<p>Target Versions and Orders are now semantically disjointed. This means that you may have a timelog over an issue associated to a Target Version and the timesheet accounting that on a different Order (GUI to do that will be introduced incrementally). Nevertheless, they are still related in that a shared Target Version can still be configured as Orders defined in common projects.</p>
<p>Timelogs over issues associated to a shared Target Version will be accounted by default on the same Order.</p>
<p>Spent time reports (/time_entries/report) use Orders as a new split criteria. Activities and issues can therefore be analyzed both for project management purposes (via Versions) and for accounting purposes (via Orders).</p>
<p>Global Orders can be shared to projects and used with issues for accounting purposes.</p>
<a name="10"></a>
<h3 >1.0<a href="#10" class="wiki-anchor">¶</a></h3>
<p>First stable version</p> 0.0.1https://www.redmine.org/plugins/redmine_app_timesheets#1.5.32013-12-16T17:05:48ZMassimo Rossello