Page History

...

• Every JIRA ticket should be sufficiently described. 
• There should not be any tickets with title only and without description. 
• If there is a discussion pertaining to the ticket, the ticket should have a link to the dev list.

Working on

...

a ticket

• Anyone in the community can start working on any unassigned ticket. 
• (OPTIONAL) It is recommended to clarify the relevance and correctness of the ticket in the community before doing actual implementation. To do this, you can write an email to the dev.list and wait for answer.
• Before beginning working on a ticket, you should assign the ticket to yourself.
• Move the ticket to IN PROGRESS state.
• If necessary, add comments describing the design decisions or approach you plan to take.
• If the changes implemented under the ticket require changes in user documentation, create a related documentation ticket (add "Documentation" to the Component field) and provide a reasonable amount of details in the ticket's description. If there is no need to change user documentation, uncheck the Docs Required flag. The Docs Required flag is used to filter out the tickets that require documentation.

Review Process and Maintainers

...