4 Common Jira Challenges and How to Overcome Them

Facebook
Twitter
LinkedIn
Pinterest
WhatsApp

Introduction

As a system admin or a project manager you often find yourself torn between management requirements and users who find the tools not as comfortable as they would like them to be. Jira is without a doubt a tool that can raise mixed emotions among users. Lucky for you, most of the users’ challenges can be easily handled.

 

1. Complex workflows and too many required fields

The challenge:

The most common challenge users experience when working with Jira is complex workflows. Many project managers love to stay in control and with Jira’s capabilities it’s quite easy to do; You make users fill required fields, add screens and validations between status changes and in no time you have created the most complex workflow ever! Congrats! But hey –  what about the end users?

Can we handle it?

When creating workflows, plan ahead, stop every few minutes and think how would you feel if you had to pass this workflow for every issue. Create simple workflows that have minimum requirements from the end user. If possible, assemble the required fields into one screen before closing an issue. Trying to think like users will help you find many non required fields that can be removed from the system. Win win situation.

 

2. The many views confuse users

The challenge:

Putting aside addons that enable more issue views, any Jira user can view a single issue on several different screens; An issue can be opened on a full screen view, or as a ticket with some details on a board. Also, it can be viewed on a quick view on your board or in a search query with defined fields. Different views can cause confusion between team members, who may miss critical information if working with a view different from the other team members.

Can we handle it?

If you are working with a board, I would suggest fitting the quick view to provide the needed details so it will provide the best view for your needs and everyone will be able to work inboard mode. If it’s not possible and working in board mode will not be sufficient, you can make it a collaborative team decision which view they all agree to work with.

 

3. Excel is still required; Jira cannot provide me everything I need

The challenge:

Many times, project managers can find themselves looking at Jira and trying to figure out how to do a simple thing but just cannot. It may also be a simple automation that you thought should be integrated into any Jira project yet it seems Atlassian does not agree with that.

Can we handle it?

Yes, there are things that you can’t do in Jira such as calculation of velocity by team vacations, or mixed reports of story points and time estimation combined. yet, in most cases you can extract everything from Jira. You just need to know where to look; As stated on issue #2 above, there are many ways to view issues and there are many ways to find what you are looking for. Even if Jira wasn’t able to provide what you needed, in most cases you can easily find an addon for this purpose.

 

4. It takes a lot of time to load pages

The problem:

When working with Jira on a daily basis you may feel that Jira becomes slower over time; It takes more time to load pages and extract queries; Editing issues may take more time to perform and the frustration makes you use Jira less and less.

Can we handle it?

The most common reason for  slowing down is too many admin privileges and uncontrolled changes. The first thing you want to do is  removing privileges from users that don’t need them. If they need an extended super user then create one but don’t give them admin. The 2nd step is to remove addons that are not in use and make it a difficult process to request more addons. Let good old bureaucracy help you. Next you need to remove and unite as much custom fields as possible. Then do the same with the workflows. In most cases you can use the same workflows and similar fields for at least 80% of your projects.

 

Conclusion

Jira doesn’t come with a manual for best practices, but still, it is expected from you, as a project manager or as a system administrator to know it all. There is a huge database of answers online, but if you can’t find what you needed, you can always contact an expert. if your team experiences difficulties or you have found other solutions for the mentioned problems, please share with us in the comment section below.

Categories:

Tags:

AI Artificial Intelligence
Continuous Improvement
EOS®
Jira Cloud
Accelerate Value Delivery At Scale
Agile Community
Systems Thinking
Managing Risk on Agile Projects
Product Management
Agility
Nexus
Scrum and XP
Frameworks
Nexus and Kanban
QA
Sprint Retrospectives
Lean Budgeting
Engineering Practices
Tips
Agile Release Management
Continuous Deployment
Kanban Basics
Agile Marketing
Business Agility
Certified SAFe
Nexus Integration Team
WIP
Agile Assembly Architecture
Operational Value Stream
Kanban Kickstart Example
System Team
Agile Basics
Nexus vs SAFe
Software Development
POPM
Coaching Agile Teams
Continuous Delivery
Scrum Master Role
Code
Scrum Master
Agile Development
Agile and DevOps Journey
AgileSparks
Self-organization
Agile Games
Change Management
Hybrid Work
ARTs
Scrum.org
Slides
SAFe DevOps
PI Planning
Agile India
Scrum Guide
Managing Projects
Continuous Planning
Scrum With Kanban
Elastic Leadership
Pomodoro Technique
ART Success
Professional Scrum Product Owner
Lean Startup
Built-In Quality
Process Improvement
Agile Games and Exercises
System Integration Environments
Release Train Engineer
Jira Plans
Achieve Business Agility
ATDD vs. BDD
speed @ scale
Agile Risk Management
Agile Delivery
Games and Exercises
Continuous Integration
LAB
Advanced Roadmaps
Implementation of Lean and Agile
SPC
The Kanban Method
LeSS
Quality Assurance
Sprint Iteration
An Appreciative Retrospective
Agile Mindset
Product Ownership
Lean Agile Basics
Lean Agile
Development Value Streams
Kaizen
Value Streams
Applying Agile Methodology
Nexus and SAFe
Video
A Kanban System for Software Engineering
Planning
Agile Project Management
Program Increment
Agile Exercises
Scrum Primer
Reading List
RSA
Legacy Enterprise
Agile Israel Events
Covid19
Large Scale Scrum
Principles of Lean-Agile Leadership
Lean Agile Organization
Scrum
Spotify
Lean Agile Leadership
Sprint Planning
Professional Scrum with Kanban
Lean and Agile Techniques
Scrum Values
Risk-aware Product Development
Limiting Work in Progress
Manage Budget Creation
Kanban 101
Effective Agile Retrospectives
Atlaassian
Agile in the Enterprise
Presentation
SAFe
Agile Project
Agile Contracts Best Practices
ALM Tools
DevOps
Lean Software Development
Agile Techniques
Introduction to Test Driven Development
Scaled Agile Framework
The Agile Coach
Agile
Kaizen Workshop
Portfolio for Jira
Risk Management in Kanban
Agile for Embedded Systems
Agile Product Development
Lean Agile Management
NIT
ROI
Agile Outsourcing
System Archetypes
Agile Testing Practices
Daily Scrum
Lean-Agile Budgeting
Agile Release Planning
Agile Product Ownership
Professional Scrum Master
BDD
GanttBan
Kanban Game
Lean-Agile Software Development
IT Operations
RTE Role
Perfection Game
ScrumMaster Tales
speed at scale
Agile Program
Introduction to ATDD
Releases Using Lean
Entrepreneurial Operating System®
Amdocs
ATDD
Webinar
Kanban
Test Driven Development
Jira
Rapid RTC
Enterprise DevOps
SAFe Release Planning
Risk Management on Agile Projects
Acceptance Test-Driven Development
Lean Risk Management
Artificial Intelligence
lean agile change management
Iterative Incremental Development
Legacy Code
Lean and Agile Principles and Practices
TDD
Software Development Estimation
Story Slicing
PI Objectives
AgileSparks
Logo
Enable registration in settings - general

AgileSparks Newsletter

Subscribe to our newsletter, and stay updated on the latest Agile news and events

academy@agilesparks.com

WELCOME

to our new website

WELCOME

to our new website

This website uses Cookies to provide a better experience
Shopping cart