Blockers flag submissions that require input from you or a customer. They are generally requests for information that will help Bugcrowd ASEs clarify any issues and unblock progress on a submission. For example, if the steps to reproduce an issue are incomplete or unclear, an ASE may ask you to provide additional details or context.
Blockers help ASEs collect much-needed information and provide better visibility into the submission's current state. Each time a blocker is created or resolved, the activity is logged in the submission's activity feed.
To help you identify submissions that are blocked, an alert can be seen directly from your Submissions Page. The alert notifies you that the submission has been marked by a Bugcrowd ASE as blocked and needs something from either you or a customer.
From the submission, the blocker can be found at the top as a page alert. The page alert includes a brief description and identifies whom the submission is blocked by. Ex: "Waiting on the researcher to provide information" would indicate the ASE is waiting on further information from you.
Bugcrowd ASEs will provide further context of the blocker in a comment in the activity feed.
Searching for Blockers
Generally, submissions that transition between the "New" and "Triage" states may require more information as they are being reviewed. Therefore, blockers will appear more often on submissions in these two states.
To easily blockers, you can filter your submissions by the new and triage states.
To resolve a blocker, you need to provide the information in a comment on the submission and check the Notify Bugcrowd Operations that the blocker is resolved box – then select the send message button.
After you resolved the blocker, it will be updated on the activity feed and a green checkmark icon will indicate the blocker has been resolved.