What licenses do I need? This is all very confusing...

Jason Rapp

I am trying to see what I need for my Software Engineering team and I am getting very confused on what software / licenses I really need. Here are the things I would like to do:

1. Manage workflow for a team of 100 users (most of these users are not specifically software engineers, but they need access to enter new work items / bugs / requirements, and to view project status, etc.).

2. I have about 25 users that are involved in software development. Right now we are working off of a few SVN repositories, however we are looking at converting the repos to GIT.

3. Code Peer reviews done over a web interface for 25 users.

4. Documentation peer reviews done over a web interface for 100 users.

5. Potentially automated builds.

 

 

 

Dave Theodore [Coyote Creek Consulting]

Don't feel bad.  The way some of the licensing works is a bit complicated.

1. Assuming you don't intend to exceed 100 users, you would want to buy a 100 user "Jira Software" license. If you have 101 users, you will need to make the jump to the next higher tier. If the user can log in, they consume a license, so it doesn't really matter whether they are only looking at issues or if they are a project manager that lives in Jira.
2. Bitbucket is Atlassian's Git environment.
3. Code review in Git is called "Pull Requests." This is built-in functionality, so you don't need a dedicated tool for this. 
4. I'm not exactly sure what you intend to do here, but Confluence might be the right tool for the job. It is essentially an enterprise wiki, but it is a great platform to bring content from the rest of your Atlassian tools in to pages in order to aggregate content and avoid context switching.
5. Bamboo is Atlassian's CI/CD tool.