Opened 10 years ago

Last modified 10 years ago

#11618 closed defect

Adding a TicketQuery in the description of a report mess up with edithours.js — at Version 2

Reported by: konubinixweb@… Owned by: Joachim Hoessler
Priority: normal Component: EstimationToolsPlugin
Severity: normal Keywords:
Cc: Trac Release:

Description (last modified by anonymous)

When putting a TicketQuery report in the description of a report. The first ticket in the report is associated to the first estimatedhours field found, that is the one of the first row of the real report.

The next ticket is associated to the next row and so on.

Let's say I have in the description of the report 

	Ticket	Summary	Type	Component	Milestone	Keywords
	#333	Some Summary	 Defect	 Some component	Some milestone

And in the real report: 

	Ticket	Summary	Component	Milestone	Owner	Type	Resolution	Remaining Hours
	#444	Some Summary	 Defect	 Some component	Some milestone 		 some owner	 Defect		 8

Then if I click on the 8 to change the value of the estimatedhours (thanks to edithours.js), the estimatedhours of 333 is modified, not the one of 444.

I added to the ticket a patch that I hope fixes the problem.

Change History (4)

Changed 10 years ago by konubinixweb@…

Attachment: 0001-Make-sure-the-estimation-cell-is-really-the-one-asso.patch​ added

comment:1 Changed 10 years ago by Ryan J Ollos

Description: modified (diff)
Summary: Adding a !TicketQuery in the description of a report mess up with edithours.js → Adding a TicketQuery in the description of a report mess up with edithours.js

comment:2 Changed 10 years ago by anonymous

Description: modified (diff)

Fixed typos

Changed 10 years ago by anonymous

Attachment: 0001-Make-sure-the-estimation-cell-is-really-the-one-asso.2.patch​ added
Note: See TracTickets for help on using tickets.