Single product, multiple platforms. Track requirements via Epic or Story?

[Stewie Griffin]

Our company has JIRA and Confluence. Our business is a single product spanning multiple platforms. I've created a custom field called "Platform" in JIRA that has all the platforms listed in a dropdown. When the Product team wants to request a new feature, they create an Epic, select the Platforms they want it to apply to, then create a Story for each platform, link it to the Epic so they can be marked resolved/done separately. Epic remains assigned to Product while the stories are with Development. Is this the correct approach?

The other option is to have Product create requirements/improvements/features on Confluence instead, create x number of stories one for each platform it should apply to, and have the link to Confluence in the description of the stories.

What's the best practice?

[Julia Levcovets]

Hi Stewie, I like your process. But, maybe you should use Components field, if it doesnt used for other purpses, then you recieve different leads in components and different bonuses.