Pivotaly enables you to keep your work in sync with pivotal tracker without having to switch between the applications. Start, stop, finish and deliver stories that you are working on right from vscode.
View story details
View details of the story you are working on - description, id, name, type, story state, tasks and blockers
Mark a story as started
Mark a story as unstarted. Implemented as stop story
Mark a story as finished
Mark a story as delivered
Deliver and undeliver tasks
Mark tasks as complete or incomplete
Resolve and unresolve blockers
Mark blockers as resolved or unresolved
Assign a story to a git branch
Member cycle time
View cycle time per members per iteration
Change story state
View member cycle time
1. Git (Optional)
Pivotaly can rely on git branches for an efficient flow. i.e. Pivotaly assumes a single pivotal tracker story corresponds to a single git branch.
A story id is prepended or appended to a git branch to link a story to a branch automatically. e.g ft-edit-read-me-345 will assume 345 is the story id.
2. Pivotal tracker API token
Pivotaly requires an API token for private pivotal tracker boards.
Pivotaly contributes the following settings:
pivotaly.protectedBranches: Array of git branches that are ideally not feature branches e.g. master. Pivotaly will not attempt to link a story to git branches added.
pivotaly.branchDelimiter: Delimiter string or RegExp to use to retrieve story ID. e.g. set to '-' to get id 345 from ft-edit-read-me-345 or '_' to get 345 from ft-edit-read-me_345 or [\/-] to get 678 from feature/678-read-me
Pivotaly may not track check-outs from bare repositories as expected.