Alternative to duplicating user stories for each component/platform

[caiello]

My company develops apps for iOS, Android, and mobile. Many of our projects have identical requirements for all three platforms, however, the dev teams and QA are often moving at different paces. Currently, every user story is duplicated for each platform. This allows each team to move at its own pace and QA to silo testing by platform. However, this leads to a lot of overhead because if the story changes, new details added etc., it has to be changed for all three copies of the ticket. This leads to a lot of challenges. What alternatives are there to manage this? One thing I've been considering is a tool that would allow us to manage the requirements outside of the ticket in one central document, like Confluence. The issue that creates is that every ticket would basically have an empty description and just a link to the Confluence page. It's pretty inconvenient to have to basically have two windows open (Jira and Confluence) for every ticket. So an ideal solution would offer something external where the requirements are documented on one place, but can natively display on a user story in Jira. I've only just begun looking for such a solution, but thought I'd see if the community had any suggestions. Surely we are not the only company that faces this. 

Thanks!

[Jack Brickey]

Hi @caiello , in my opinion requirements for a feature definitely belongs in something like Confluence. This is especially true if those requirements are applicable across various platforms like in your case. Jira issues in and of themselves should not define the overall requirements. Rather there should be a Jira issue that outlines the effort to complete a single requirement.