Agree Marta. Keep it constrained. I don’t always like the idea of testing a product based on it’s “features” and doing one at a time, or only testing my teams own features and not other team’s work. But this might be a good one to set a boundary on and make certain features or pages out of bounds or excluded as a way of keeping focus around the key product risks by excluding “non-risk” pages from the bounty.
I would be tempted to give extra score for bugs that are “quick-to-fix” 
.