It would depend on how you wanted to manage it. We have a project made of many parts, and some parts interact with others, so we have separate projects.
Each part could be (for example):
If it's a smaller app I would be include to just create a single project and prefix my issues/tickets with a reference to it so I could quickly filter results or label the issues.
Thank you for your response!
It isn't small or simple app. Parts relate to each other only logically. For example mobile and web apps works with the same data. But It doesn't share any module between platforms.
We also distinguish every platform like product. So customer can order one, two, three products (platforms).
Also developers usually don't work on multiple platforms.
Is better approach split platforms to separate projects?
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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