This is an archived page. Since this article was first published, some features and interface elements have been changed. Please, visit our Knowledge Base for an updated version.
We are glad to announce the first integration (more are to come) with a version control system that we’ve released. From now on 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. Pretty convenient, don’t you think?
Below is a screenshot of an example commit, which by the way changed the task color and deadline:
This is how this works in three simple 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 Administrator user or a standard 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.
Kanbanize supports the following commands in the SVN commit message:
#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)
Change in the logging module. #id 1234
Change in the logging module. #taskid 1234
1234 Change in the logging module.
#title, #description, #priority, #assignee (with alias @<username>), #color, #size, #tags, #deadline, #extlink, #type
All of these Kanban card parameters can be changed via a commit message using the format of the Kanbanize API values.
Change in the logging module. #taskid 1234 #priority high #color ffaaff #deadline 2014-12-12 @Peter
1234 Change in the logging module. @Peter
You can also move a task via the commit message. The supported parameters are:
#column – The name of the column you want to move the task into.
#lane – The name of the lane you want to move the task into.
#boardid – If you want to move a task to another board, specify the board id.
#position – The position at which you want to move the task to.
#exceedingreason – If you are to exceed the WIP limit, provide a reason with this parameter.
1234 #column Done
1234 #column Done #lane bugs #boardid 12 #position 1
We also support a bunch of move shortcuts that make your lives 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 Done section
#<section> last – Move a task to the last column in the Done section
<section> can be any of the following: requested, in progress, done
To log time via the commit message use the following parameter:
#loggedtime – The number of hours you want to log to the task.
1234 #loggedtime 2
You could also block or unblock a task via the commit message. The supported commands are:
#block – the reason with which you block the task
#editblock – specify this parameter if the task is currently blocked and you want to change the block reason
#unblock – unblock the task
1234 #block “Not enough resources.”
Happy coding with Kanbanize!