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.
It might sound a bit pedantic but whereas 'Issues' really makes sense as a naming convention, calling the container that organises issues a 'project' doesn't seem right as a project has a start and and end by definition.
I'm curious and I wondered if it was a throwback to the early versions of the product or if there was any explanation as to where 'project' came from as a naming convention?
I actually feel happy about Issue, I used to associate issue with problem but by definition, it's just an important topic. I like the implication that anything you take the time to physically type through the interface is important.
We actually managed to really engage service desk users with 'ticket' terminology. It all came out of one senior ops person saying they needed a way to give everyone a number like you get at the meat counter in Sainsbury's 😂 (they were struggling with too many requests via email, text message, carrier pigeon etc.). So you could argue that the entitlement a ticket gives is the access to a service or expertise.
Project however, makes no sense to me 😆 but I guess the origin story would explain where it came from. I wonder if there is a book by Mike and or Scott like James Watt's Brewdog book. Quick Google search suggested not.
I really questioned the term project recently when exploring the Initiative/Epic/Story/Sub-task hierarchy with someone and they wanted to know why project wasn't in the hierarchy. I explained it as a container, for issues, which made it easier for us to understand.
Recently I was describing our internal system to a new team member and this was one of the trickier areas to explain.
We eventually agreed that a "Jira Project" is a container. We have different types of containers (project categories) that hold different things. i.e. some Jira Projects are containers for work tasks which are assigned to people and put in sprints, others are containers for artifacts that store information we use in Confluence reports like customer environments with current version or soft copies of all contracts.
Some weeks ago I asked to the community about what Jira project means in its instances:
In my opinion a Jira project is a box where you can save your issues... by default a Jira Project is not a project. For this reason we created Profields, if you want to take your projects to another level, you should use Profields: