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

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?

1 answer

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.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Monday in Jira Software

How large do you think Jira Software can grow?

Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...

418 views 6 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you