How to work with Epics, Themes and Initiatives in Confluence (NOT Jira) ?

Question

I have tried to understand how to work with Epics, Themes and Initiatives in Confluence, but I have only found information about how to create Epics in Jira and assign Issues to Epics there.

But I would very much like to be able to structure User Stories in Confluence, by using Epics, Themes and Initiatives.

Is this possible?

If it is, how do I do it?

You could say I would to do some Structured Requirements Management in Confluence and only Confluence, I do Not wish to involve Jira.

Best Regards,

Christian

Diego_88dj6o · Answer

Christian, glad to know that I was able to clarify our tools for you! If you need anything else, let the Community know.

CR8.IT.2019 · Answer

Hi Again,

Yes, I am now a very happy camper!

Now both tools make sense to me :-)

Best Regards,

Christian

Diego_88dj6o · Answer

Hello again Christian!
The definition of User Stories I have taken in consideration can be seen in this post:

* Project Management - User Stories

You could take a look there and check if we are referencing the same thing. I would hate to give you information that does not apply to what you are striving for.

If we are talking about the same objective currently, I can guide you to use one of our Page Templates From Confluence. You can check a little bit more about templates for Cloud and Server here:

* Blueprints and user created templates - Confluence Cloud
* Page templates - Confluence Server

There is a chance that you need to use our Product Requirements Template to organize the content you created:

* Product requirements blueprint
* How to document product requirements in Confluence

Strictly speaking, there is no wrong way of using Confluence. It all depends on your business needs. However, not everything is available from within a single application. Creation of issues, sprints, user stories and a lot more is handled by Jira. Confluence can then gather those items and structure them in a way that Makes Them Shareable And Can Constitute Documentation for reference, for example.

You can surely Create Spaces For Different Projects, for example. Where each page deals with a different aspect of said project and then links with different Jira issues in your Jira instance, effectively documenting everything and summarizing information. Here is a little more information on Confluence:

* Confluence - Spaces
* Organize your work in spaces - Confluence 101
* Create content with pages - Confluence 101

Putting it simply, Confluence was devised as a documentation tool for the tracking of issues and bugs done in Jira. But both of them can work separately and have many other features within.

Confluence can document the action done in Jira (Issue tracking, for example) and make it easy for users to share and collaborate within Confluence itself.

Let me know if this clears things up Christian! Looking forward to your reply.