A number of fields are common between the CSR issue type and normal bug/RFE issue types and between the CSR issue type and the JEP issue type. Unless otherwise noted, by default the fields in common among different issue types are used in analogous ways in each issue type with the field.
If a field has not been set, the field may not be displayed. To set such a field, when logged in hit the "Edit" button of the CSR issue.
Description: pre-populated with CSR template. The CSR template has four sections, Summary, Problem, Solution, and Specification. Follow the stated instructions on how to provide the requested information for each section.
Assignee: the engineer who is currently the person primarily responsible for advancing the proposal. The assignee may change over time as different people work on the request.
Priority: JIRA default field. Not used by the CSR process.
Labels: Free-form text
Component & Subcomponent: the technological area of the proposal; same classification scheme as used in the JDK project. If the proposal spans multiple areas, choose the area comprising the largest fraction of the proposal or break the proposal into multiple CSR issues.
Status & Resolution: State of the proposal in the CSR process. There are seven basic states captured in the Status and resolution fields:
...