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 have 1 huge project. We keep getting new requirements for the project for which we create Epics/backlogs.
We also come across bugs for which we created a separate project called as "QA"
Since the application is huge, I need to refactor some code. Refactoring of the code is an ongoing activitiy and I see this as a part of "Kanban".
My question, how can I do this all in 1 single project or do you recommend seperate projects ?
Hi @csawai1
I would do it all in one project and use different Issue Types to separate the work. You could also use Components to identify the work, but with Issue Types you can use separate workflows for each type and even different screens if you are using a lot of custom fields in the project.
You can still use components to "categorize" the different types of issues within the issue type if needed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.