<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=299788&amp;fmt=gif">

4 Secrets of Highly Performing Jira Project Administrators

Atlassian, Jira, Agile

Guest Contributor: Mary Ramirez

As an Atlassian Support Lead, I often speak to clients about implementing best practices for their Jira instance. Some are new to Atlassian products, others are experiencing a large company growth, and many are simply trying to work more efficiently. Many organizations want to take full advantage of Jira’s capabilities and easily become overwhelmed. At Isos Technology, we offer our clients ongoing support and training tailored to get the most out of their Atlassian tools.

Pointer #1: What do you need?

It’s important to discuss and organize the needs of your project before requesting it from your Jira administrator. Starting your project in an organized manner will save your organization from having to reorganize it in the future.

Prior to placing the request with your Jira administrators, discuss the following items with your team:

What type of team will be utilizing this project?

This will give the Jira administrator insight on which Jira template to utilize. Utilizing the proper Jira template will create your project with default configurations.

For example:

The Scrum and Kanban software development template gives you a Scrum or Kanban board and various issue type to include Epic and Story.
The Task management template gives you issue types like To Do and Done.

Will you use a shared configuration or the default configuration?

It’s vital to use a configuration scheme that aligns with the project's needs. The Jira Administrator has the option of creating a custom project or creating the project utilizing a shared configuration.


Shared configuration

Pro’s: The workflows and screens from other projects are already created. This doesn’t impact Jira performance, creates less work for the Jira administrator, and creates a standard across projects.

Con’s: Personal changes to the project cannot be made because they’re shared with others. It’s important to think long-term and identify whether the project will need custom issue types, screens, etc.


Default configuration

Pro’s: New screens, screen schemes, field configuration, conditions, transitions, and validators can be made to tailor to the project.
Con’s: Many of the customizations may have to be done by the Jira administrator. Too many schemes can impact Jira’s performance.


Pointer #2: Who’s doing what?


In determining your project needs, your team may conclude that different people may play different roles. Jira allows you to allocate particular people to specific roles in your project.

It’s important to determine the following roles:

  1. Project Administrator can edit project role membership, edit workflows, screens and define project components and versions. It’s recommended that the project administrators have extended project permissions in order to make additional workflow and screen edits.
  2. Project Lead manages the project and can be used as the default assignee for project issues.
  3. Members are the only individuals who have access to your project.
  4. Scrum Master project role allows the user to manage sprints.


Pointer #3: Do you need issues auto-assigned?

In Jira, project administrators can create components and assign component leads. Therefore when an issue is created and a component is chosen, the ticket will automatically be assigned to the designated user.

For example: If an issue’s component is set to Database when it’s created, the issue will automatically be assigned to the component lead, Emma Paris.



Pointer #4: Do you need visual of your issues?



Every new project starts with a vision. Whether it’s a vision of an app release or analyzing data, it’s easier to view this information in a form of a picture instead of a list of issues.

Reports allow users to aggregate data from projects or filters and present it in one sitting. Pie charts can be added as a gadget to your dashboard and/or be shared with others, allowing your team to be updated every 15 minutes.

Awesome, you have a chart in place and you’re using it during your business development meetings. But now your supervisor wants to see the break-down. No worries! Charts can be downloaded to different formats like CSV and Word to provide a more detailed description.

See below for an example:


Managing JIRA at Scale White Paper

TAGS: Atlassian, Jira, Agile

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Subscribe to Our Newsletter

Recent Blog Posts

Blog Archives

See all