# 0.31.1 `elements issue search` takes one quoted query and lists the issues you filed with `-mine`. A long issue body is passed on standard input. ## Changes - `elements issue search` takes the query as one argument in quotes: `elements issue search 'hot reload loses form state'`. Text piped into the command is the query when the argument is left out. - `elements issue search -mine` lists the issues you filed, newest first. - `elements issue search` and `elements issue show` print the standard report: the state, then sections and rows. A search result is the id, the title, the part of the issue that matched and a line of details, and `-json` output has `snippet` and `answered`. - A closed issue has a resolution: `fixed`, `implemented`, `answered` or `declined`. `elements issue show` prints it with the release that carries the fix, and `-json` output has `resolution`. - `elements issue new` and `elements issue comment` read a long body from standard input. The `-body-file` option is removed. - `elements -h` shows three examples: create an app, start it, read the manual. - `elements man issues` has a "Following Up" section on reading the answer to an issue you filed. ## Upgrade ### Pass an issue body on standard input `-body-file` is removed. Redirect the file into the command. Before: ```bash Terminal elements issue new -kind=bug -title='Hot reload loses form state' -body-file=report.md ``` After: ```bash Terminal elements issue new -kind=bug -title='Hot reload loses form state' < report.md ``` ### Quote the search query Before: ```bash Terminal elements issue search hot reload loses form state ``` After: ```bash Terminal elements issue search 'hot reload loses form state' ```