Requirements: Confluence + Jira or jira enough?

Question

Hi guys,
i have seen a lot of tutorials where the requirements are created first in confluence and afterwards added to jira. Would it not be enough to create them only in jira?

I can list all requirements in confluence via a Jira/Filter makro, if i need so.

The benefits are:

* When i change requirements in jira they're synchronized automatically with confluence.
* Jira handles tables and states better.
* Its easier for developers. They dont need to jump between pages, everything is on one place.
* If i need a more powerfull editor, i can create a page for the issue in confluence later. And the good part is, i would have a unique title for the page, cause i would use issue id for the page title as prefix.

Disadvantages:

* No history feature for issues in jira?

Thanks for your attention.

Mr. Poopybutthole · Answer

Thank you,

i will stick with my approach then and if it doesnt work out i change it.

Nic Brough -Adaptavist- · Answer

There is a full issue history on all Jira issues (unless you choose to delete them)

I personally tend to write a story in Jira and then go to Confluence if it turns out it needs writing up in a longer form for some reason.  I'd agree with your points about Jira being an issue tracker and handling process, and developers being in one place.