In May, we rolled out a bunch of cool updates, so straight to the point.
- Collective scoring (ICE / RICE) and poker planning inside Kaiten🔥
– improved burndown chart for Scrum commands,
– new periods in the “Throughput” graph,
– the timeline shows the planned and real time of work on the task.
– PlantUML support in the card description,
– adding any fields to scheduled tasks,
– checking due dates for parent cards when changing the deadline for child cards.
- Configuring notifications for checklist items.
- GitHub and GitLab: support for multiple id cards in one commit message.
Collective scoring (ICE / RICE) and poker planning inside Kaiten
Fire feature! You can now prioritize tasks using the ICE / RICE technique right in Kaiten.
How to setup
- Create a special field for assessing each factor
Menu → Custom properties → Add Custom property. In the “Type” field, select “Collective value”.
2. Create a field for calculating the collective mark
Menu → Custom properties → Add Custom property.
In the “Type” field, select “Formula”.
3. Add the created fields to the card, fill in the values
4. In the field with the formula, you will see the final grade of the task
Improved burndown chart for Scrum teams
Now changing the size of the card during a sprint is correctly displayed on the graph and does not affect the total approved size of tasks at the beginning of the sprint.
After the sprint is completed, its burndown chart will not change, even if the size of the unfinished tasks is changed.
Configuring notifications for checklist items
If the deadline for a checklist item is changed, Kaiten will send a notification to the cardholder who is responsible for the card and is responsible for completing this item in the checklist.
If you do not want to receive these notifications, turn them off in the settings. Go to the menu (with the stripes in the upper left corner of the screen) → Profile → Notification settings. Uncheck the box “Due date changed”.
GitHub and GitLab: support for multiple id cards in one commit message
If a developer has made a fix for several tasks in one commit, then he can add comments to all tasks with one command.
How to setup
To do this, in the commit message, you need to specify the Kaiten card numbers separated by commas. For example,
“Fix bug #101234,11277,34888”.
PlantUML support in card description
Draw graphs and diagrams in the card description using PlantUML. This will help you better convey the meaning of the task to the performer and avoid mistakes. For example, clearly explain to developers what should happen with a certain user action.
How to setup
Enter PlantUML commands in the Description field. The list of graphs that can be built and the commands required for this can be found on the official PlantUML website.
After saving, the system converts the commands into a schedule.
New periods in the “Throughput” graph: half a year, a quarter and two weeks
Now you can see how many cards were created during the specified periods and how many of them were completed. This will help balance your team’s work.
Adding any fields to scheduled tasks
You can pre-add tags, checklists, attendees, and more to your card. Time savings are evident!
To create a scheduled task, click on the orange clock icon in the panel on the right.
Planned and real time of work on the task on the timeline
The timeline now has visual indications for the scheduled time and for real-time work on the task. Now you can easily see the difference between plan and reality.
Checking due dates for parent cards when changing the deadline for child cards
Kaiten takes care of the order in your projects. Therefore, if you change the due date for a child card, the system will offer to check the deadline for the parent card and update it if necessary.
That’s all! If you have any questions about any update, write to the chat, we will help you figure it out and configure.