Rename the previous org-clubhouse-headline-from-story to
org-clubhouse-headline-from-story-*id*, and make -headline-from-story
use prompt-for-story to allow autocompletion of the title of the story
to pull down.
Allow (configurably) creating stories with Clubhouse labels based on Org
tags, either creating all labels or only using labels that already exist
in Clubhouse
Upcoming should be an `org-clubhouse-update-story-labels` command.
Make task headline story-ids links just like the IDs for the story
headlines are, so that they can later be read by
org-clubhouse-extract-story-id - this fixes task status updating, which
was broken.
When pulling stories from clubhouse by any method (either
headline-from-story or headlines-from-query) also pull down the list of
tasks on the story as children of the headline.
Fixes#15
Add a configuration parameter,
`org-clubhouse-claim-story-on-status-update`, which allows updating the
assignee of stories on status update, either always or for specific todo
keywords
The various prompt-function callbacks get called on another thread,
meaning we can't wait for them to return to set the value. This moves
the flow control for story creation so it actually happens if you don't
have a default story type set
Merges in a function which has existed in my local setup for a while now
to run a query to Clubhouse and create all the results as org headlines
at a specified level
Defines an 'org-clubhouse-update-story-title' interactive function. Can
only be invoked if cursor is over the Headline title
fixes string-to-int -> string-to-number (unsupported as of Emacs 26)
Expose a `org-clubhouse-default-story-type` variable that can be set to
`feature`, `bug`, `chore` or `prompt`. If set to `prompt`, the
org-clubhouse `Create new story` flow will prompt for the story type
each time. If set to any of the other values, the `Create new story`
flow will use that value for all new stories until that variable is set
otherwise.
This also exposes a new interactive function called
`org-clubhouse-set-default-story-type` that prompts users to set the
default story type value.
I'm not sure `quelpa!` is a function...
```
Debugger entered--Lisp error: (void-function quelpa!)
```
...additionally, is `:files ("*")` necessary? Looks like the `(package! ...)`
was copy-pasted and package -> quelpa. Does this hold up?
As committed, this allows creating Clubhouse tickets from a heading in org-mode,
and then updating the status of those tickets when the Org status updates
