When the “write functional spec” task is complete, it is sent for review. If the spec is satisfactory, the review results in approval. However, there are times that the spec is returned for updates (new version) throughout the project life cycle and new versions need to be created.
The goal is to create a counter so that each time a completed task is reopened it will add 1. This will provide easily reportable data on the number of iterations.
This scenario is not limited to document iterations. Another example is testing to count the number of times a scenario is tested and retested before it passes.
My initial thoughts are to create a number column called “Iteration” and create a rule that adds 1 to the value in the field each time the task status is changed to in progress. I am not able to figure out how to get that to work. Using a formula value for this field isn’t working.
Any suggestions would be helpful. The goal is to not have to go into the task history to manually count the number of times it changes. Having the iteration count makes it easily reportable.
… then you’ll see a more complex problem solution, but you could implement the core elements (basically a number field and a formula field) and it should help you solve your issue.
I am looking to count the number of iterations required to achieve a successful outcome. Basically, a counter for the number of times a task is reopened after it is marked complete.
@Samara_Lippsett, I find it hard to give detailed workflow advice in a Forum like this (as opposed to a hands-on virtual meeting), but perhaps others will weigh in.