Using JIRA for Bug Tracking
Configure JIRA for Bug Tracking
So you want to use JIRA to track some pesky bugs? These steps should help you setup your instance so you'll have some data to explore in the Key Features section next!
- Create a Project
- Create Issues
- Create Users
- Configure Permissions
- Setup Useful Integrations and Add-ons
Are you currently using another bug tracker or trying out other products besides JIRA? See how JIRA stacks up against the competition. If you're thinking about making the switch from IBM Rational Clearquest, we've created some resources just for you. Check them out!
Create a Project
Before you can create issues, you need to create a project to contain them.
- Click 'Administration' then 'Projects' under the 'Projects' tab. 'Add Project' is at the top right.
- Project Key is the short prefix for issues: 'ABC-XXX'. Note that this cannot be changed later.
Documenation: Defining a Project
Learn how projects, issues, and workflows fit together in this 2 minute video:
Now get some data in JIRA!
Documentation: Creating an Issue
Unless you're exploring JIRA alone, you should start out by adding other users to your instance.
- From 'Administration,' select 'Users,' then 'Add User.'
- Locate the new user and click the 'Groups' link in the far right column.
- Select the appropriate groups for the new user:
- 'jira-users' can create and edit issues
- 'jira-developers' can create, edit and log work (time spent) against issues
- 'jira-administrators' has full access to Administration
- note: these are simply defaults - you can change them later.
After you've added the user to a group, you should edit their role within your newly created project.
- Click 'Project Roles' in the far right column, then click 'Edit Project Roles.'
- Here, you can change the roles that the selected user has for each project in your instance.
Once you've chosen who plays each role in your projects, you can use those roles to define project permissions. By default, permissions are setup for roles - rather than individual users or groups. because of this, those roles, and hence the connected permissions, can be changed per project. This is especially helpful if you have a large number of users to maintain and want to keep JIRA administration restricted to just a few.
Global Permissions apply to JIRA as a whole: things like who can log in, created shared filters/dashboards, and perform bulk changes.
Project Permissions control who can edit, delete, and perform other issue actions within a project.
Documentation: Managing Project Permissions