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

This widget could not be displayed.

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
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted 5 hours ago in Europe

Topic Tuesday: How did you learn about the AUG programme?

Back in 2010 I hadn't been using the Atlassian tools (JIRA, Confluence, Bamboo) that long and I started searching online to see if I could chat to other users primarily about how they used the produc...

13 views 0 0
View post

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