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
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 am pretty new to the Jira products and have a question about Projects, specifically, how they "should" be used. For example, would you expect to have a project defined for specific "things" like Proposals, Licensing, Internal, Sales and Marketing, where each of those would relate to various products you develop? To me, this doesn't seem appropriate and you should have artifacts of each of these types within a given project. Am I correct in that a project should be inclusive of an entire body of work and everything associated with that should be within the project?
Let me give an example.
We have a software product APP1
App1 has a product backlog with many issues, tests, etc.. There will be many test plans executed against it, normal stuff. Also, there will be proposals, licensing, sales initiatives, etc. all specific to this APP1. So, shouldn't ALL artifacts of all types (issues, tickets, tests, sprints, etc.) all be within this one project? It seems backwards to me to have multiple projects where some of your projects are components/artifacts of others. This feels like were creating a very messy many-to-many relationship between projects and my understanding was that a Project should encompass the entire body of work and all things related to that project.
Any feedback on this would be greatly appreciated.
Hi @Bob Boursaw
Jira is a tool to help your teams collaborate and manage your work items. How your teams work is how they work, and so there isn't really a "best" practice; perhaps only better/worser ones based upon the features and limitations of the tools supporting the teams.
Consider what you need to do and know to help you decide one Jira project or multiple; types of boards, types of dashboards, desired add-on products, etc. And, what you need to know in order to improve over time.
For example, you note several types of work such as proposals, licensing, sales initiatives, and probably delivery and support in your Value Stream. How do those separate things happen (workflow) and what do those teams want to know about how they work (measurement)? Is this one team that does all types of work, from concept to cash, or several teams?
If one team, one project may help. If multiple teams, or one team would find value in separate reporting (progress, lead time, etc.), perhaps separate projects could help. There are Jira features that can help as work items bridge between projects, so that is less of a constraint.
And, if you pick a direction and that is not working out for your teams, you can evolve to a different method. Perhaps start by listing what you need vs. want, and then see how Jira can help.
Thanks, and best regards,