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