Updated Changelog

Reporter is not generally editable.

CHANGELOG.md

@@ -1,5 +1,10 @@
 # Changelog
 
+## 0.1.3 - 2016-07-30
+
+* [[#43](https://github.com/Netflix-Skunkworks/go-jira/issues/43)] add support for jira done|todo|prog commands [Cory Bennett] [[dd7d1cc](https://github.com/Netflix-Skunkworks/go-jira/commit/dd7d1cc)]
+* Reporter is not generally editable. [Mike Pountney] [[a637b43](https://github.com/Netflix-Skunkworks/go-jira/commit/a637b43)]
+
 ## 0.1.2 - 2016-06-29
 
 * [[#44](https://github.com/Netflix-Skunkworks/go-jira/issues/44)] Close tmpfile before rename to work around "The process cannot access the file because it is being used by another process" error on windows. [Cory Bennett] [[0980f8e](https://github.com/Netflix-Skunkworks/go-jira/commit/0980f8e)]

README.md

@@ -157,6 +157,26 @@ When running a command like `jira edit` it will look through the current directo
 if found it will use that file as the template, otherwise it will use the default **edit** template hard-coded into **go-jira**.  You can export the default
 hard-coded templates with `jira export-templates` which will write them to **~/.jira.d/templates/**.
 
+#### Writing/Editing Templates
+
+First the basic templating functionality is defined by the Go language 'text/template' library.  The library reference documentation can be found [here](https://golang.org/pkg/text/template/), and there is a good primer document [here](https://gohugo.io/templates/go-templates/).  `go-jira` also provides a few extra helper functions to make it a bit easlier to format the data, those functions are defined [here](https://github.com/Netflix-Skunkworks/go-jira/blob/master/util.go#L133).
+
+Knowing what data and fields are available to any given template is not obvious. The easiest approach to determine what is available is to use the `debug` template on any given operation.  For eample to find out what is available to the "view" templates, you can use:
+```
+jira view GOJIRA-321 -t debug
+```
+
+This will print out the data in JSON format that is available to the template.  You can do this for any other operation, like "list":
+```
+jira list -t debug
+```
+
+Figuring out what is available to input templates (like for the `create` operation) is a bit more tricky, but similar.  To find the data available for a `create` template you can run:
+```
+jira create --dryrun -t debug --editor /bin/cat
+```
+This will attempt to fetch metadata for your default project (you can provide any options that you would normally specify for the `create` operation).  It uses the `--dryrun` option to prevent any actual updates being sent to Jira.  The `-t debug` is like before to cause the input to be serialized to JSON and printed for your inspection.  Finally the `--editor /bin/cat` will cause `go-jira` to just print the template rather than open up an editor and wait for you to edit/save it.
+
 ## Usage
 
 ```

main/main.go

@@ -65,6 +65,9 @@ Usage:
   jira reopen ISSUE [--edit] <Edit Options>
   jira start ISSUE [--edit] <Edit Options>
   jira stop ISSUE [--edit] <Edit Options>
+  jira todo ISSUE [--edit] <Edit Options>
+  jira done ISSUE [--edit] <Edit Options>
+  jira prog|progress|in-progress [--edit] <Edit Options>
   jira comment ISSUE [--noedit] <Edit Options>
   jira (set,add,remove) labels ISSUE [LABEL] ...
   jira take ISSUE
@@ -140,6 +143,11 @@ Command Options:
 		"reopen":           "reopen",
 		"start":            "start",
 		"stop":             "stop",
+		"todo":             "todo",
+		"done":             "done",
+		"prog":             "in-progress",
+		"progress":         "in-progress",
+		"in-progress":      "in-progress",
 		"comment":          "comment",
 		"label":            "labels",
 		"labels":           "labels",
@@ -390,6 +398,18 @@ Command Options:
 		requireArgs(1)
 		setEditing(false)
 		err = c.CmdTransition(args[0], "stop")
+	case "todo":
+		requireArgs(1)
+		setEditing(false)
+		err = c.CmdTransition(args[0], "To Do")
+	case "done":
+		requireArgs(1)
+		setEditing(false)
+		err = c.CmdTransition(args[0], "Done")
+	case "in-progress":
+		requireArgs(1)
+		setEditing(false)
+		err = c.CmdTransition(args[0], "In Progress")
 	case "comment":
 		requireArgs(1)
 		setEditing(true)

templates.go

@@ -65,8 +65,8 @@ fields:
     - name: {{ .name }}{{end}}{{end}}
   assignee:
     name: {{ if .overrides.assignee }}{{.overrides.assignee}}{{else}}{{if .fields.assignee }}{{ .fields.assignee.name }}{{end}}{{end}}
-  reporter:
-    name: {{ if .overrides.reporter }}{{ .overrides.reporter }}{{else if .fields.reporter}}{{ .fields.reporter.name }}{{end}}
+#	reporter:
+#	  name: {{ if .overrides.reporter }}{{ .overrides.reporter }}{{else if .fields.reporter}}{{ .fields.reporter.name }}{{end}}
   # watchers
   customfield_10110: {{ range .fields.customfield_10110 }}
     - name: {{ .name }}{{end}}{{if .overrides.watcher}}