Search
Close this search box.
Search
Close this search box.
Search
Close this search box.

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.

Subscribe for Email Updates:

Categories:

Tags:

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

Contact Us

Request for additional information and prices

AgileSparks Newsletter

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

This website uses Cookies to provide a better experience
Shopping cart