iteration

[Ivan Andrieiev]

in the tasks, there is an iteration field, each iteration is the discovery of new bugs, it changes automatically from the Reviem status to the In Progress status, you need to have statistics in the form of a diagram, how many bugs were there in each iteration?

[Jack Brickey]

Hi @Ivan Andrieiev , I am confused by this question. Can you please reiterate what you are asking for here?

[Ivan Andrieiev]

@Jack Brickey  Hi

maybe I wrote it wrong
1. There is a testing task.
2. A new iteration is added each time the task changes to the In progress status.
3. When testing, new problems of the "Bug" type are created
4. Each bug is linked to this testing task.
5. After testing and identifying bugs, the task changes to In Review status.
6. After fixing the bugs, the task returns to In Progress status and the next iteration takes place (the iteration field changes from 1 to 2).
7. In the second iteration, the QA finds bugs and returns them to the In Reviem status.
I am interested in the number of bugs that were linked during the first, second, etc. iterations.
It may have become even more complicated, so you can ask clarifying questions.

[Jack Brickey]

I see. I guess the first potential solution for this that comes to my mind would be to create three custom fields: Iteration (values of One and Two), Iteration One Bugs, Iteration Two Bugs. These last two fields would be a number, Field,, representing a count of the number of bugs linked to the issue during the specific iteration, they would default to zero. Then you would have an automation rule that would trigger on an issue being linked. You would use conditions to assess which iteration you were in and increment the appropriate iteration bug count field. Does this make sense?

[Ivan Andrieiev]

@Jack Brickey 

so this is a good idea, can you tell me how to set up such automation?