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