You can input the Epic directly from Jira by using the Jira macro. Some of the most important elements that you’ll enter into your new Product requirements page are the Page title and the Epic. Now that this page is created, you’ll see on the top of your page that the page title and other page properties are left blank for you to fill in – except for the creator which is automatically placed as the Document owner – which can be changed.

If you are unfamiliar with creating Product requirements documentation, this is a pretty good jumping off point. We’ll use the Product requirements template. You’ll create a new page in your space, and be prompted to use a template or a blank page.

Let’s start with creating your Product requirements page in your Confluence instance – it does mean you need to already have a Confluence space setup, that can be selected. It can even contain details in the Epic you’ve already created, and acceptance criteria put into the description field of your user story for you. Visualization and Useĭid you know you might not ever have the need to write Jira issues – user stories at least? Atlassian has made it easier to take your well-developed user stories right into Jira. Collaborating on the proposed user stories to refine the list in Confluence with your team before deciding to put them into Jira can be significantly rewarding once development begins. The need for someone to copy and paste, or even create manually, issues into Jira that come from a document is a horrible waste of resources and efficiency. I am going to share with you how to make these tasks easier and faster. Writing good user stories that capture the needs and detail acceptance criteria takes time and thoughtfulness.

How to use confluence and jira together