Support calculated fields in TFS
This suggestion is migrated to Developer Community. Please use below link to view the current status.
The ability to create work item fields which are based on a calculation of the value of fields in linked work items.
For example, if a Product Backlog work item has two children Task work items which each have remaining work, it would be incredibly beneficial to have a field on the Product Backlog work item that was able to roll-up the values of these fields. That is to say that if the remaining work on the two Tasks for that Product Backlog item were 5 and 10 respectively, the Product Backlog work item could show that the sum of the remaining work was 15.
Calculated fields should be able to be based on the link type and the work item type.
Your consideration for this functionality is appreciated.
Lina Cruise commented
Such an informative post.
I like to sum up backlog items' effort and set it at their parent effort field.
krishan kant commented
I would like to create a custom field which can calculate 'Aging' of the WI based on comparing @today and @createddate. It will be very helpful to see this number on the backlog board.
Even thins as simple as Filed A+B would be handy for charting the results. Though a SQL Case statement would be amazing!
Christopher Mank commented
This is a huge YES from me and my current client. This is so needed.
Calculated fields--even if implemented with language/syntax similar to SSRS reporting (which would lower the learning curve and possible shorted development time).
Grouping is another wish!! Although, the tree capability is similar, multi-level grouping and aggregates in reporting would be amazingly useful! These aggregates could be used in very unique ways with tile widgets and charting.
You can use VSTS RollUp extension which calculates remaining work based on original estimate and completed work. Also does rollup from Task to top level of work item type like PBI,Feature and Epic.
Ashok Linner commented
No response from Microsoft this request?
I too would like a generic calculated field, for instance "Complete" which is a boolean where it's complete only if Status = Closed, and not complete otherwise. That would be advantageous on dashboard controls which have limited aggregation controls.
Emiel Jongerius commented
I would like to have a generic way to calculate fields. For instance: I would like to be able to calculate the Risk Score by multiplying the Risk Likelihood by the Risk Impact.
I'd like a calculated "Days in State" field, and "Days since created". Then I could also set card style rules on these to highlight work that has been slow to progress across my Kanban Board.
Its great recommendation however I think the problem is mush deeper and it is due to the lack of support of aggregation in WIQL for workitems and linked workitems. WIQL is really getting old and limited and I haven't seen any serious improvement in last 10 years. I think TFS query system needs a boost right now.
TFSAggregator for Online would be just another feature.... but calculated fields can be reference fields... like auto calculation of remaining ours from Original Estimate minus Completed Work = Remaining effort... something like this...
Don VanVooren commented
This would really help out for items like bugs where i've had to add a second Effort section to the WI to track QA & DEV time.
Reuben Swartz commented
It would also be nice to be able to configure a roll up for status also. For instance it would be wonderful if we can set that if a feature had children that were marked as being in progress that it would roll up to the parent also.
Vince Aimutis commented
This is a good request and would be great functionality as it would allow a TFS summary level work item with rolled up values to be published and/or refreshed from Project (if you use a TFS-Project integration), rather than having to publish/refresh every granular level task allowing a PM to manage to a higher level of detail than the granular task level often needed by developers.
Michael L commented
In on-premises TFS TFSAggregator can handle this. It's pretty flexible on rolling up data.
Brandon Stanley commented
I don't understand why it can't handled
fieldValue = fieldValue + 1