You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I've entered a new company and they are trying to use Jira. We all are new to this. What I've found out is that we are developing one product, and they have several projects for every Delevop Team (iOS, Android, Windows, etc). We want to use Epics in order to filter the issues. I don't know if i could use the Compounents option to categorize some of the issues instead of Epics, because we thought we could use same epics in different projects.
I'm looking for more tips about issues types, ways to categorize, and good use of Epics. This is a product that will be going on stores soon and, unfortunately, will be receiving new feedback from now on. Should we start a new whole project involving everything? so we would have only one compounent for each epic that we use to categorize? Or just leave those epics as categories?
I now is up to us, but I want advices please.