dolibarr-bugtrack
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Dolibarr-bugtrack] [Bug #854] Users can approve their own holiday reque


From: Doliforge
Subject: [Dolibarr-bugtrack] [Bug #854] Users can approve their own holiday requests even if not in validation group
Date: Fri, 03 May 2013 14:15:33 +0200

Doliforge
Is this email not displaying correctly?
update email preferences.

Users can approve their own holiday requests even if not in validation group

Latest modifications

2013-05-03 14:15 (Europe/Paris)
The bug has been corrected inside GIT sources
(http://www.github.com/Dolibarr/dolibarr).

So fix should be available with next stable release.
Changes:
  • Step to reproduce bug: 
- 
+Usage of a dedicated group for a feature deos not match dolibarr rules. We must use a dedicated permission for that and if user want to use group, user must allow permission to group. This is a main change so not possible to include it into stable branch. It will be fixed only into3.4 
  • Resolution: 
NoneFixed

Answer now

Snapshot

 Details
Last Modified On:  2013-04-26 07:39 Submitted by:  Marcos García (marcosgdf)
Submitted on:  2013-04-26 07:39 
Summary:  Users can approve their own holiday requests even if not in validation group
Description:  Users can approve their own holiday requests even if not in validation group
Step to reproduce bug:  Usage of a dedicated group for a feature deos not match dolibarr rules. We must use a dedicated permission for that and if user want to use group, user must allow permission to group. This is a main change so not possible to include it into stable branch. It will be fixed only into3.4
Version:  3.3.1 Category:  Module: Holidays
Severity:  7 OS Type/Version:  
PHP version:   Database type and version:  
 Status
Status:  Open Assigned to:  Marcos García (marcosgdf)
Resolution:  Fixed 

Comments

Laurent Destailleur 2013-05-03 14:15
The bug has been corrected inside GIT sources
(http://www.github.com/Dolibarr/dolibarr).

So fix should be available with next stable release.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]