...
Please refrain from editing descriptions and comments if possible, as edits spam the mailing list and clutter JIRA's "All" display, which is otherwise very useful. Instead, preview descriptions and comments using the preview button (icon below the comment box) before posting them.
Keep descriptions brief and save more elaborate proposals for comments, since descriptions are included in JIRA's automatically sent messages. If you change your mind, note this in a new comment, rather than editing an older comment. The issue should preserve this history of the discussion.
To open a JIRA issue, click the Create button on the top line of the Hive summary page or any Hive JIRA issue. When in doubt about how to fill in the form, take a look at what was done for other issues.
Please leave Note that Fix Version/s should empty when creating the issue – it should not be tagged until an issue is closed, and then, it is tagged by the committer closing it to indicate which the earliest version(s) the fix went into. Instead of Fix Version/s is not used s, use Target Version/s to request which version it should go into – such requests can be made in the comments.versions the new issue's patch should go into. (Target Version/s was added to the Create Issue form in November 2015. You can add target versions to issues created before that with the Edit button, which is in the upper left corner.)
When in doubt about how to fill in the Create Issue form, take a look at what was done for other issues. Here Here are several Hive JIRA issues that you can use as examples:
...