Refine your first feature with Delibr
In Delibr, everything starts with a document. Create documents for feature requirements, new products, or anything where you have to move from insights and discovery, through discussion, and then quickly into action. (By ‘action’ we mean creating user stories in Jira.)
This guide will help you set up your first document, invite your teammates, and push your first ticket to Jira using the Delibr Jira integration.
Create a new document
Go to the document dashboard and click “Create new document.” You can create a blank document or use a pre-filled template. For the discovery, discussion, and refinement process around a new feature, we recommend the Epic Refinement template. It gives you a ready-made, tidy outline structure to work with.
Structure your outline
This guide focuses on using the Epic Refinement template. In a template, you just replace the placeholder content with your own. To move things around, drag and drop sections using the hamburger menu (find this by hovering to the left of the bullet you want to move). You can also remove or add sections wherever you need to.
Start by naming the document. This will become the name of the epic when you link the refinement document to Jira.
Whether you’re using a template or starting with a blank document, it’s also valuable to grasp the expand/collapse functionality of Delibr. Your parent bullets will become your table of contents, as shown in the images below.
You might want to name the subsections by competence, outcome, or area, depending on who you will invite and how collaborators gives input.
Now, let’s put the document into action.
Planning, refinement and discussion are rarely solo efforts. Now it’s time to invite your colleagues to add input and collaborate.
In the upper-right corner of the document, you’ll see “Invite”. Here you can invite individual people, or you can make the document visible to your team. To do this, choose “Make team visible” in the sharing function.
In the invite modal, you can control permissions, and/or add an optional personal message (just like in Google Drive).
Now you can make decisions together and turn those into user stories. When you’re ready, it’s time to turn those into tickets and push them to Jira.
Push your first ticket to Jira
If you haven’t connected Delibr to Jira, do that first. Only a Jira administrator can do this, so if that’s not you, you might have to invite them to Delibr.
Open the hamburger menu of any bullet in the document. Choose “Jira”, and then follow the three-step guide that pops up. Once this is established, any bullet you create in a Delibr document can be pushed to Jira.
Now, go to the bullet you want to turn into a Jira issue, click the hamburger menu, and then choose “Jira”.
In the Jira modal, choose the type of issue, and then hit “Add” to add it to Jira. You can view it in Jira by clicking the link in the bullet.
Note that Delibr pulls in the bullet you push, as well as all the nested bullets under it.
The information contained in the nested bullet tree structure in Delibr will be visible in the Jira ticket via the Delibr Jira Plug in.
Want more help? Book a demo
We have Delibr experts who can walk you through this, or any other function or feature in the tool. Open the scheduler and pick a time here.