...
Blocker - For testing, this means that testing cannot progress without a fix and this should be the priority. For a production application, this means that required operations of the observatory are halted. An immediate fix is required, unless there is an agreement to an alternate plan by the parties involved. If you are submitting a Blocker for a production application BE AWARE that the developers will interpret this as a requirement to continue to work after hours until a satisfactory resolution is agreed upon.
Workflow Transitions
Initial Reporting - The Component should be identified. If you can't find an appropriate component, assign to a more general component that makes sense, or ask SSA. The ticket will be assigned to the Component Lead in the SSA group for further review and assignment to a developer. DO NOT change the assignee or the Fix Version as this just circumvents the normal workflow and increases the chances that something gets dropped. We periodically review incoming tickets so we should catch even these cases, but it just requires more effort. For Engineering Tasks, the developer may assign the ticket to themselves, but don't assign a Fix Version as all tickets need to be prioritized based on available resources. After initial reporting, the ticket will be Open.