While the chat option is available in every test cycle to clarify doubts, severity-related expectations are sometimes not explicitly discussed or confirmed in time—especially in fast-paced cycles. This can lead to valid bugs being rejected simply because they are not deemed critical enough.

To improve this process, I suggest:

Clearly communicating severity expectations within the test scope, ideally with examples for clarity.

Allowing bug submissions to include an optional note such as “Valid but not critical” for team leader or developer consideration.

Implementing a “soft submit” or “review-only” tag for educational or informative bugs that may not qualify for payout but provide valuable insights.

This would help testers better understand expectations, reduce frustration over rejections, and support a learning environment.