Focus...

Once you have decided what the focus will be on, you certainly will find new bugs. So what now?

Just like in the real world, you probably aren't going to wash your car with the FULL car wash program because a little bird made a little mess.

The same applies with the planning of testing a bug. You can apply an indicator which shows the amount of test effort that will be used.

The main point here is: the test approach and test policy should clearly have a gradation in it just like this as an example! Apply it, use it.

It doesn't have to be exactly like this, you can have your own version. But you gotta alternate in attention and effort.

If you apply something like this, with a field in Jira, for example:

Then you have got to determine what program means what actions.

For example: low-program = 1 layer of test pyramid and only sanity checks, full program = 3 layers, regression testing, all test automation has run, and... you decide the programs!

Once you have determined and described the level of programs, you can state in the Definition of Done: