A Few Common Jira Problems I Faced and How I Fixed Them

[#1]

Hi everyone ,

I’ve been working with Jira for a while now, and in my project I came across a few common challenges. Sharing a few of them here along with what worked for me. These are simple things, but they made a difference in day-to-day work.

1. Multiple components getting selected

In our case, we needed only one component per issue, but Jira allows multiple selection.

What I did was use an automation rule to keep just one value and remove the rest. It doesn’t stop users from selecting multiple, but it helps keep the data clean.

2. Weekly status reports taking time

We were preparing weekly reports manually, which was repetitive. 

I started using Jira data with Rovo to generate summaries. It’s not 100% perfect, but it definitely saves time and gives a good starting point.

3. Duplicate tickets

We noticed the same issues getting created multiple times.

I tried using JQL checks and basic automation to identify similar issues and notify users. Still improving this, but it reduced duplicates.

4. Workflow steps getting skipped

 In some cases, users were skipping required steps or not filling mandatory fields. 

I added validators and a few automation checks to make sure required details are captured before moving forward.

Final thoughts

From what I’ve seen, it’s hard to control everything directly in Jira. Using automation to handle things in the background worked better for me.
 

Curious to know

Would be great to hear how others are handling similar challenges, or any new ones you’ve faced feel free to share.

[Thorsten Letschert _Decadis AG_]

@M Chandra Shekar Some interesting takes. I'm particularly curious about #1: how do you/or your automation rule decide which component is the "right" one, then? Will the user be notified of what happened and why? 

[M Chandra Shekar]

Thanks for asking! The automation rule keeps the first component added as the ‘right’ one and removes any additional components added later. Currently, users aren’t notified automatically, but we can consider adding a notification if needed.

[Trudy Claspill]

Hello @M Chandra Shekar 

For #1 have you considered instead having a single-choice select list? Or is there an aspect of Components that you need in this situation, such as enabling the Space Admin to manage the list?

For #3 Duplicate tickets - does that concerning Business, Software, or Service Spaces?

For #4 Workflow steps getting skipped - what are the steps getting skipped, besides not filling in required information? Are items not being transitioned through statuses in the correct order/path? For that, you might consider using targeted Transitions rather than global Transitions, and using Conditions to check the current state of an item to determine if the transition should be allowed.

[M Chandra Shekar]

 1. We are keeping components only so space admins can manage list dynamically.

2. Duplicates mainly a concern in business and software projects

3. Sometimes users skip mandatory fields in a specific state, so we’re considering targeted Transitions with Conditions to enforce the correct workflow.

[TOMIZAWA Yumi_Ricksoft_]

Hi @M Chandra Shekar 

How about this free Marketplace app? It lets you create a custom field for a single-choice component picker.

https://marketplace.atlassian.com/apps/1238364/component-picker-for-jira-cloud