Created by: mramm
Created date: 2010-03-18 01:43:36.063000
Assigned to:nobody
You can't actually edit a sum field when there are sub-tasks, but it acts like you can, and when you do it gives you a traceback.
Discussion
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by mramm:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by mramm:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by wolf:
assigned_to: Max Ischenko --> Wolf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by wolf:
assigned_to: Wolf --> nobody
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by dean:
assigned_to: Wolf --> nobody
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by wolf:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by mramm:
Talked to nate, and this is how he wants it to work. So there's the value for THIS ticket in the sum field itself, and another value for the total that gets displayed in parens next to the data from this ticket.
Est. Time (Days): 0.25 (total: 5.1)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by mramm:
I think perhaps we should just adjust the way sum fields work, so that there's a separate place where sum fields sub-ticket values are summed up, as well as a place where the value lives. This eliminates possible confusion, and allows time to be assigned to a master ticket -- and it's subtickets.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by wolf:
assigned_to: Wolf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by mramm:
milestone: alpha2 → alpha3
custom_field__est_time_days: 0.25 → 1.0
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by dean:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by mramm:
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-07-07
Originally by: sf-overlords
Post by noostendorp:
status: accepted --> open
milestone: beta2 --> someday-maybe
custom_field__size: -->
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Originally by: sf-overlords
Post by mramm:
Originally by: sf-overlords
Post by mramm:
Originally by: sf-overlords
Post by wolf:
Originally by: sf-overlords
Post by wolf:
Originally by: sf-overlords
Post by dean:
Originally by: sf-overlords
Post by wolf:
Originally by: sf-overlords
Post by mramm:
Talked to nate, and this is how he wants it to work. So there's the value for THIS ticket in the sum field itself, and another value for the total that gets displayed in parens next to the data from this ticket.
Originally by: sf-overlords
Post by mramm:
I think perhaps we should just adjust the way sum fields work, so that there's a separate place where sum fields sub-ticket values are summed up, as well as a place where the value lives. This eliminates possible confusion, and allows time to be assigned to a master ticket -- and it's subtickets.
Originally by: sf-overlords
Post by wolf:
Originally by: sf-overlords
Post by mramm:
milestone: alpha2 → alpha3
custom_field__est_time_days: 0.25 → 1.0
Originally by: sf-overlords
Post by dean:
Originally by: sf-overlords
Post by mramm:
Originally by: sf-overlords
Post by noostendorp:
status: accepted --> open
milestone: beta2 --> someday-maybe
custom_field__size: -->
description has changed
- status: open --> closed
- custom_field__priority: low --> 0