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:

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