dolibarr-bugtrack
[Top][All Lists]
Advanced

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

[Dolibarr-bugtrack] [Bug #1731] Can't use quick navigation on project ta


From: Doliforge
Subject: [Dolibarr-bugtrack] [Bug #1731] Can't use quick navigation on project tasks secondary tabs
Date: Mon, 22 Dec 2014 22:52:57 +0100

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

Can't use quick navigation on project tasks secondary tabs

Latest modifications

2014-12-22 22:52 (Europe/Madrid)
Changes:
  • Assigned to: 
NoneMarcos García (marcosgdf)
  • Resolution: 
NoneFixed

Answer now

Snapshot

 Details
Submitted by:  Raphaël Doursenaud (rdoursenaud) Submitted on:  2014-11-26 11:37
Last Modified On:  2014-12-04 12:08 
Summary:  Can't use quick navigation on project tasks secondary tabs
Description:  Quick navigation (blue arrows) don't work on secondary tabs (Ressources, time consumption, notes…).
Step to reproduce bug:  It seems to work fine if all tasks have been created sequentially but misbehaves if you have, say, deleted a project and created a new one.
Detected in version:  3.6.1 Category:  Module: Projects
Severity:  5 - Major OS Type/Version:  
PHP version:   Database type and version:  
 Status
Status:  Open Assigned to:  Marcos García (marcosgdf)
Resolution:  Fixed 

Comments

Raphaël Doursenaud 2014-12-04 12:08
A very simple way to reproduce is to create 2 project with 1 each and then create another task on the first project so that you have something like that:
+------------+---------+
| Project ID | Task ID |
+------------+---------+
| 1 | 1 |
| 2 | 2 |
| 1 | 3 |
+------------+---------+

Then go to the first project's first task.
Notice you can use the arrows on the card tab.
Now switch to the resources tab for exemple and try to use the arrow.
You'll be greated with a "ErrorRecordNotFound".
You'll get the same result on the time consumption tab but without the error message.
SPANGARO Alexandre 2014-12-03 06:18
Sorry Raphaël, I Don't find the way to reproduce the problem.

The problem comes probably from a sorting based on ref instead of id ?


reply via email to

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