New Portfolio Lane
Kanbanize 5.11 introduces a new Portfolio lane. It allows you to have a master view of the Initiatives and their progress via work breakdown structure and Initiative/child cards linking.
The Portfolio Lane is an additional swimlane that could be activated from the Show Portfolio Lane icon at the upper side of your board interface. It has three main columns: "Requested"; "In Progress"; "Done" that can not be modified.
An Initiative could stand behind a Project/Feature/Epic story, etc., while the Child cards represent the deliverable components, which outline the Initiative and should be executed by the project team.
You can easily create a new Initiative using the +New Initiative icon.
To create a dependency between the Initiative and the cards/deliverables-> drag & drop a card from the Team Board swimlane and attach it to the corresponding Initiative or vice versa.
Upon linking the card as a child, the Initiative card flips and refreshes, visualizing the linked cards through small rectangular icons that hold information for the cards/deliverables (on hover). Each icon has a specific color representing the current card position in the workflow:
- blue stands for the "In Requested" column
- orange stands for "In Progress" column
- green stands for in "Done" column.
When you move a card (deliverable) on the Team board to the "In Progress" stage, the Initiative card will automatically move to "In Progress", indicating that the Initiative has been started. In case that a deliverable is blocked the Initiative card will be blocked too.
The Initiative has a progress indicator that shows the percentage of completed cards. The Cycle time of the Initiative and its deadline (if set) are visible too.
When all deliverables are moved to "Done, the Initiative progress indicator will become 100% and the card will move to "Done" as well.
More details about the Portfolio Lane can be found in the dedicated Hot to Article: Portfolio Kanban Lane in Kanbanize
Note: The system allows you to convert a card to an initiative by simply drag & drop a card and positioning it to the portfolio lane.
Copy Cards and Create Links by Drag & Drop
Version 5.10 introduces and enhanced and very easy way of copying cards and creating links. Just press the Ctrl. key and drag & drop it to a new position to create a simple copy of the card. To create a link between cards, press the Ctrl. key and drag any of your cards on top of another. Select a link (child/relative/predecessor/successor) from the popup window and the cards will be automatically linked with each other.
Enhanced Jira Integration
Kanbanize 5.11 includes a set of improvements of the integration between Kanbanize and Jira.
- Kanbanize board structure complies with the Jira workflow rules: when a card is created in Kanbanize, the current card column (e.g. Requested) is compared to the Jira issue status. If they don't match, the card will be moved to the column corresponding to the Jira status. If there is no column corresponding to the Jira issue status, the Kanbanize card will be moved to the Backlog and a comment will be added to the card, notifying about the error.
- Card Type mapping: configuring your Kanbanize board and creating card types that match the type names of the Jira issues will help you integrate the tools smoothly.
- In case that a new Jira issue triggers a Kanbanize card creation and there is no card type matching the Jira issue type, Kanbanize will automatically create a type with the same name.
- If a new Kanbanize card triggers a Jira issue creation and the Kanbanize card type is set to "None", Kanbanize will randomly detect a Jira type and set it as a property on the card.
- Kanbanize card title includes issue key - each Kanbanize card corresponding to a Jira issue will have the Jira issue key displayed in the card title.
- Error Handling:
Jira to Kanbanize - when an error is detected a notification email will be sent to the user whose API key has been used in the webhook URL.
Kanbanize to Jira - when an error is detected a notification email will be sent to the user who triggered the action in Kanbanize.