Are you a Scrum practitioner and lover? Then you will be happy. Damn, you’ll probably be happy even if you don’t use Scrum; this feature is very useful for so many reasons… User Stories are here!! Many of you have been requesting this directly or indirectly. We’ve had plenty of feedback requesting the possibility of extending the functionality of sub-tasks, like supporting user assignation, individual estimated costs… For some of you, a task with a simple checklist is more than enough, but those who want to have more granularity and plan things to the little detail often missed these features as a way to create small detailed tasks without having to deal with many many cards on the boards. Before this release, the only way of grouping those tasks under a high-level feature concept was the GDM, which of course is still useful, but the problem was you couldn’t manage those tasks as one when working on boards or the backlog. Now, we put user stories in between the design element and the tasks, adding an optional new layer of grouping between the design concepts and the detailed tasks.
We also added some other small improvements and fixed a few of bugs. Let’s take a look at the details!
First of all, let’s introduce a new concept that you’ll see everywhere on the HacknPlan UI from now on: the work item, or just item for short. Due to the addition of a new type of element similar to tasks that can coexist at the same level, we needed to introduce a concept that refers to both tasks and user stories in a generic way. A work item represents a unit of work that can be added to boards, the backlog and other lists, that can be of two types, task or user story, with some special features each. When we refer to work items on the UI or documentation, we are talking about tasks and user stories indistinctly.
Note: Due to this naming change, some file and field names of the data export feature have changed, so if you are processing those files in any way, you should update your scripts.
A User story in HacknPlan is very similar to a task and contains mostly the same fields and information than a task does. The main differences are:
- Unlike tasks, user stories can’t be assigned to a category; instead, they are automatically assigned to a special category called ‘User story’ that allows you to filter and get metrics about stories in a unified way. The reason for this is user stories refer to features from a high-level point of view, they don’t go deep on the details of the implementation, they define what should be the outcome and what’s the value for the player.
- User stories can’t have sub-tasks; instead, they can contain regular tasks as child items. The tasks within a user story are not displayed on the kanban board, but still they have their own stage, assigned users, costs… as a list of items inside the user story. You can establish estimations, log work… both at user story or task level, and they will be aggregated to provide total metrics.
This feature opens up many new possibilities when it comes to splitting your work in smaller chunks and distributing it among your team. It also simplifies boards, backlog, metrics… by hiding the internal details of user stories while keeping all the functionality of tasks available inside.
You can create a user story from the same places you can create a task (left menu, board, GDM…), and also using the keyboard shortcut “U” from anywhere in your project. There also are some other actions at your disposal that can help you managing stories:
- You can convert an existing task to a user story (existing sub-tasks will be converted to full tasks) and also convert a user story to a task (story tasks will be converted to subtasks, preserving their completion status). This is available at the actions dropdown on the work item editor (ellipsis button on the top-right corner).
- You can add an existing task to a user story, by clicking on Send to -> User story on the editor.
- You can move a task or user story to the next or previous stage from the context menu (right click or click on the ellipsis icon on the card).
- We added two new filter fields: Creation date and Creator (user).
- In the automatic work log dialog launched on work item completion, you can now set a value of 0. Also, if the item you are completing has an estimation set but no work has been logged, the value is prefilled to match the estimation. This is so convenient for users who log all the work at the end, or the ones that use points as the cost metric.
- Admins can now reactivate inactive workspace and project users with just a single click.
- We added a search input to filter the icons on selection (for categories and tags).
- Users with “Update only” permissions can now set the picture displayed on the card, so they can show the progress with screenshots.
- Improved the functionality of typeahead dropdowns.
- Other small UI/UX improvements.
- Sometimes, design elements with several levels of children couldn’t be deleted.
- In some HacknPlan Studio projects, user avatars were not properly displayed.
- Saving descriptions on fullscreen could cause the application to go unresponsive.
- The burndown chart caused an annoying flickering on some resolutions and browsers.
- The closing date of items was not properly exported to CSV.
I hope you enjoy this new update! It’s been a while since the last one, and the main reason is we have been working on these features and the Public API at the same time, but we wanted to release the user stories before the API to make sure the first version already included them. We’ll keep working hard on the API to release it as soon as possible, we can’t wait to see what you guys can build with it. Also, there are many new features coming to HacknPlan Studio for multi-project management, and of course we keep listening to your feedback and bug reports to keep the tool in good shape in between releases, keep that coming 🙂