Mingle Card: 2784
UPDATE: Ross verify that both item.length and FX5__Ticket_Items__r.length work. He was unaware that we could do this and was fine using this instead of creating a new helper class.
Narrative
Acceptance Criteria
Create a count helper similar to the sum helper that we already have.
{{ count FX5__Ticket_Items__r "some_field__c"}}
Create this helper so that it works in both Mobile and Back Office
Analysis
How about just:
{{ FX5\_\_Ticket\_Items\_\_r.length }}
since there will be the same number of fields/properties per collection. Unless we are talking about only counting records that have a value for the field/property (e.g. not null)
Related Stories
Tasks
{{table query: SELECT Number, Name, Owner, 'Task Status' WHERE Type = Task and Story = THIS CARD}}
Defects
{{table query: SELECT Number, Name, Owner, 'Defect Status' WHERE Type = Defect and 'Related Story' = THIS CARD}}
githubbob42
commented
9 years ago
Mingle Card: 2784 UPDATE: Ross verify that both item.length and FX5__Ticket_Items__r.length work. He was unaware that we could do this and was fine using this instead of creating a new helper class.
Narrative
Acceptance Criteria
Create a count helper similar to the sum helper that we already have.
{{ count FX5__Ticket_Items__r "some_field__c"}}
Create this helper so that it works in both Mobile and Back Office
Analysis
How about just:
since there will be the same number of fields/properties per collection. Unless we are talking about only counting records that have a value for the field/property (e.g. not null)
Related Stories
Tasks
{{table query: SELECT Number, Name, Owner, 'Task Status' WHERE Type = Task and Story = THIS CARD}}
Defects
{{table query: SELECT Number, Name, Owner, 'Defect Status' WHERE Type = Defect and 'Related Story' = THIS CARD}}
Test Plan