With this integration, each SVN commit will appear as a comment of a referred task and if you want to, you will be able to change the task details, log time* or move the task to a desired location on the board* from within this same commit message.
The screenshot below shows an example commit, which changed the task color and deadline:
To set up the integration, follow these steps:
- In Kanbanize, go to Administration -> Integrations and enable SVN integration
- Download this archive and extract it into the /hooks folder of your SVN server.
- Configure the post-commit SVN hook with the corresponding URL and the API key of any Kanbanize user.
We recommend using a dedicated user (e.g. GitHub_user) with permissions to access, comment, and modify cards on the desired boards. - Use the special syntax in your commit message.
Usage:
The integration can update Kanbnaize cards through "#" hashtag commands in the message.
Track commits
#taskid / #id – this is a required parameter for the integration to work. You can provide it in one of these three formats:
- #id 1234 (can be anywhere in the commit message and takes priority if present)
- #taskid 1234 (can be anywhere in the commit message and takes priority if present)
- 1234 (must always be the first thing in your commit message)
Examples of commit messages:
- `Change in the logging module. #id 1234`
- `Change in the logging module. #taskid 1234`
- `1234 Change in the logging module.`
Update card details
#title, #description, #priority, #assignee (with alias @<username>), #color, #size, #tags, #deadline, #extlink, #type
All these parameters can be changed via the commit message using our API functions.
Examples of commit messages:
- `Change in the logging module. #taskid 1234 #priority high #color ffaaff #deadline 2014-12-12 @Peter`
- `1234 Change in the logging module. @Peter`
Move a card
#column, #lane, #boardid, #position, #exceedingreason (if you are to exceed the WIP limit, provide a reason with this parameter)
Examples of commit messages:
- `1234 #column "In Progress"` - move the card to the "In Progress" column
- `1234 #column Done #boardid 12 #position 1` - move the card to the "Done" column to the board with id 12
- `1234 #column “Done.Ready for Deployment” #lane bugs #boardid 12 #position 1` - move the card to the "Ready for Deployment" column to the board with id 12. The card will be placed in the top position in the "Bugs" swimlane.
We also support a bunch of move shortcuts that make it all easier
#move “Ready for testing/Platform Team” – Move the task to the “Ready for testing” column and the “Platform Team” swimlane
#move Development/ – Move the task to the Development column
#move “/Platform Team” – Move the task to the Platform Team swimlane
#requested – Move a task to the first column in the Requested section
#inprogress – Move a task to the first column in the In Progress section
#done – Move a task to the first column in the Done section
#<section> first – Move a task to the first column in the section
#<section> 2 – Move a task to the second column in the section
#<section> last – Move a task to the last column in the section
<section> can be any of the following: requested, progress, done
Update card status
#block, #editblock, #unblock
Examples of commit messages:
- 1234 #block “Not enough resources.”
- 1234 #editblock “Still not enough resources.”
- 1234 #unblock
Log time to card
#loggedtime – The number of hours you want to log to the task.
Examples of commit messages:
- `1234 #loggedtime 2`
- `1234 #loggedtime 0.5`