Treating confluence pages as jira issues (database items)

[Oriol Fàbregas Pujol]

Hi
We are struggling on using confluence+jira for documentation and sw development. I think the ideal would be to have a system that works similarly as Notion where pages could become items of a database in jira and where the macros of confluence worked like the issue fields in jira issues (so they were like the same thing). Maybe with apps like this (https://wallbox.atlassian.net/wiki/marketplace/discover/app/com.k15t.orderly.databases) we could do the same but I was wondering if there are other free solutions already available.

[Peter Van de Voorde]

Hey Oriol,

I wouldn't recommend trying to force one way of working (Notion) onto a completely different toolset. You might be able to pull it off but it would never work as well as you hope. (It would be like using a hammer to put a screw in the wall). 

I would recommend you to take a look at the Atlassian University courses and read through this series on how to use Jira and Confluence for Software development: https://www.atlassian.com/agile/scrum/jira-confluence-scrum 

The tools are different from Notion but have their own integrated, supported, and well-rounded way of doing documentation and sw development. 

Moving from one way of working to another can be challenging, but also rewarding as you gain new experiences and insights. 

I hope this helps.

Cheers,
Peter

[Oriol Fàbregas Pujol]

Hi Peter,
Thanks for your feedback. I will read the document you shared and try to further understand how to proceed in my company. We are currently in need of improving:

1. The way we specify products both SW and HW
2. The way we ensure traceability between requirements (in an agile way) and validation tests
3. The way we search in our documentation how a product or a specific feature works
4. The way we communicate how a product or specific feature works
5. The way we reuse requirements for new product developments.

If I find a better way of working (maybe after reading your link) I will let the community know but I see some limitations with not being able to more easily add attributes to confluence pages that are in sync to issue fields on jira issues while still keeping the power of a hierarchy tree in confluence. Will try to reflect on that.

[Oriol Fàbregas Pujol]

Maybe, improving page property macros in confluence would be enough. https://support.atlassian.com/confluence-cloud/docs/insert-the-page-properties-macro/
They are currently difficult to create and edit.
I guess that's why other companies build this kind of integrable apps: https://wallbox.atlassian.net/wiki/marketplace/discover/app/com.k15t.orderly.databases
But, this may make more sense to be a core feature from confluence.
I wonder if confluence team is thinking in so.