Age | Commit message (Collapse) | Author | Files | Lines |
|
Add function to create single story element from a prompted list of active stories.
|
|
org-clubhouse-get-headlines-in-region was returning elements in reverse
order, causing stories to be created in reverse order when multiple were
created in a region with org-clubhouse-create-story. Just reversing the
list at the end should fix that.
|
|
Make org-clubhouse-set-epic set all selected stories to the same epic if
multiple stories are selected.
|
|
The same as how we allow creating stories without epics, add a "No
Milestone" list item to the top of the list of milestones to select from
when creating an epic.
|
|
iteration-id, not project-id
|
|
Ability retrieve headlines from a single iteration
|
|
If we're not claiming a story, don't pass owner_ids to the API at all,
rather than passing it as null, which causes the API to return an error.
|
|
oops
|
|
Add an org-clubhouse-clocked-in-story-id function, for programmatically
querying the currently clocked-in clubhouse story ID
|
|
Add an org-clubhouse-set-epic command, to change the clubhouse epic of
the story at point
|
|
While it's probably a good idea to assign epics to new stories,
depending on the methodology used by the team not everything may
warrant being attached to an epic. E.g. one off task and what
not.
|
|
Creating a single story would fail if the point was not on a
header. Now the code tries to find the header for the element at
point.
|
|
For some reason, some of my stories do not appear to have state
name. This is most likely a bug (either with this mode or the
API), regardless the missing name should be handled gracefully.
|
|
v1 and v2 will be deprecated on 2020-03-01. It is unclear if v2
will still be available afterward. According to
https://clubhouse.io/blog/api-v3/ it **should** be a drop in
replacement.
|
|
Arguably, helm should be supported too, but hey!
|
|
If we pull down a story without labels, don't format the :: for those
labels
|
|
org-element-and-children-at-point was comparing the current point <=
end, but should've been <.
Fixes #17
|
|
elisp calls this 1+, I had it sitting in my utils
Fixes #16
|
|
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.
|
|
Whenever we pull stories from clubhouse, write the labels of those
stories as headline tags
|
|
Add a command to update the labels of an existing story from the labels
of an org headline
|
|
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.
|
|
Dunno what happened here or when, but update-story-at-point doesn't take
this argument and also the variable doesn't even exist
|
|
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
|
|
Implement a command that pulls down the status from clubhouse for a list
of story headlines, and updates the todo keyword accordingly
|
|
Add a standalone org-clubhouse-claim function for claiming the current
story without making any other updates
|
|
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
|
|
- Use the right URL for updating tasks
- Use the right key and value for marking task status
|
|
Add a clause to org-clubhouse-update-status to update task headline
statuses in addition to story statuses
|
|
Make all the commented-out stuff in push-task-list work properly
|
|
oops
|
|
When linking clubhouse stories to headlines, save the name of the
clubhouse story as a property on the headline - useful for reference!
|
|
Implement an interactive function for linking existing org headlines
with existing clubhouse stories.
|
|
Adds org-clubhouse-headline-from-story, which allows passing a single
story ID to make a headline from.
Fixes #14
|
|
Base the todo-keyword of a created story on its workflow-state in
clubhouse, rather than just hardcoding it to TODO
Fixes #11
|
|
Oops!
Fixes #12
|
|
This is required by default in my emacs, but needs to be required here
for people not running Doom
|
|
flycheck was complaining, plus this is good anyway
|
|
If a DESCRIPTION drawer exists on headlines being used to create
stories, it is populated as the description of the created story
|
|
Add a command to update the description of the current story with the
contents of a drawer labeled DESCRIPTION, if one exists
|
|
Add docs for all config variables and interactive commands, and list
commands in the README
|
|
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
|
|
This is nice to have, but also stick it in a drawer so it's not obtrusive
|
|
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
|
|
Allow creating stories along with a task list comprised of their child
elements
|
|
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.
|
|
Adds an interactive menu for selecting story type on story creation.
|
|
Make org-clubhouse-request a kv-function with an additional :params kv, for
supporting query params in requests
|