Sharing is caring!!! 😀

[Ashish Mani Tripathi]

Hi Everyone,

While Jira is widely praised for its effectiveness and appeal, it is important to acknowledge and address some of its limitations.

Sharing is caring!!! 😀 

Please share or comment down below your latest worst experience with Jira tool and let discuss the best practice with each other to handle those limitations.

Let's learn from others experience and gain knowledge.

Cheers!!!

[Ted]

GRABS POPCORN

[Alan Bruce]

1.  Trying to do anything with Assets and tickets/automation/workflows is not as intuitive in Cloud as compared to Data Center.
2. The Customer Request Type field does not seem to behave the same (i.e. If we add a validator in the workflow that references the Customer Request Type field, the validator does not work.)
3. Jira Assets in the Cloud does not have an option to import Users/Groups like the Data Center version.
4. Automations that include updating Asset Custom fields error randomly. (Seems like a connection blip)

Those are just a few that I have bumped into.

[Jared G]

What a fun way to start my Thursday! If I could talk to an Atlassian developer, the things I would say....

1. Firstly, could we get better navigation?!  I get it now, but it took me a solid year of being a Jira Admin to understand how to fully untie things from schemes, when to reach an item through the project vs global, and when I can access a control I need through which, or through the project summary page - it's all over the place.

2. The simple lack of functionality, and it's reliance on 3rd party add-ons.  Things like not being able to customize portals for your customers.

3. Simple limitations such as not being able to use the same form across projects.

4. So many areas that are separated when they really should be together.  Notifications - there's the customer portal area, internal area, global area...  Same with permissions - could they not put those in logical connected areas?

I'm fairly solid in the navigational areas NOW, but it was a steep learning curve for a newbie.

With all that said, all due praise to Atlassian, the improvements have been appreciated.

[Holly Scott]

I also agree with the navigation. It'd be nice if things were easy (easier) to find and consistent.

[Ashish Mani Tripathi]

Completely agree and I do atlassian has done some great job in Jira cloud. Things are pretty easy to find. But yeah they still have to do more on navigation side.

[Holly Scott]

I have to agree with Jared on, "The simple lack of functionality, and it's reliance on 3rd party add-ons." This has been so frustrating for our company. Everything we can think of to help our business with what seems like basic functions that should come with Jira is only available (if available) via paid for, subscription based add-ons. I can't thoroughly convey how much I despise subscription based anything. 

[Joe Jadamec]

In Jira Data Center, getting to the "Administer User" link is very difficult.
It requires a click, mouse over, click, click.  And if you don't get the first mouse over exactly right, the pop-up disappears.  This is very frustrating when you are trying to work quickly.

It would be much easier to user, if you either make the pop-up static (see screenshot), or add the "Administer User" option to the "..." drop down menu under Actions on the far right.

[Ashish Mani Tripathi]

I know in JSM, has done something on the same line. You will notice a small (i) icon. User just have to click this icon and user pop-up screen will appear. 

[Robin Stemmers]

Hi
This is an interesting topic.

My last worst experience was when the automation quota changed. While my company was happy with the Standard Plan, we are now forced to upgrade to Premium just to get the "unlimited/limited" quota for automation's.

It would have been great to be able to buy an "add-on subscription". It could work the same as the user pricing of sorts.

e.g. I need a 1000 more automation's on a Standard Plan.  5000 for all Service desks is ridiculous.

[Jared G]

Luckily, we weren't hit too hard with this change but it raises a frustration I have in that premium will have one solid item I need, and the cost is so exorbitantly high when compared to standard.  The fact that I can use a mixture of weird automation techniques, mixed with 3rd party add-ons to achieve things (sometimes) I need is nice, but also a frustrating business model.  These techniques create fragility in my environment, when a real assumingly working method is hidden behind a comparatively high pay-wall.

I question if Atlassian has really considered their business model as it pertains to cost and what's provided, when you can save tons of money, and sometimes get a workable solution.  Seems like they're battling themselves, and we the customer get caught in the middle of it.  The disparity between standard and premium models are daunting.

[Ashish Mani Tripathi]

That's right. You can look for alternatives like replace few automations which can achieve by workflow (validator, post-functions, condition) and if you have script runner then you can try some of them using basic scripts.

[Holly Scott]

One more because it came up in a meeting I was just in. When making changes in Jira, you get a pop-up window for confirmation, but it won't go away until you close it. Seems like it could go away after a couple/few seconds.

[Ashish Mani Tripathi]

Yeah, they need reduce the time for that pop-up message. But that's good atleast they have given us option to close it. 

[Alan Bruce]

The sandbox is not a true duplicate of the Production environment. Especially if you are using Assets.

It should not be so difficult to make a usable copy of the Production environment.

[Lakshmi Priya]

Bulk upload feature can quite straight forward - like already said some third party integrations does wonders while the out of the box feature is so confusing and tedious.

[Vishal Biyani]

The license policy of add-ons based on number of JIRA licenses. 

If you have x number of JIRA licenses, and say you want to get an add-on for your testing team which could be possibly x/10, still you need to pay the license cost for x users. This makes it prohibitively expensive to use some good add-ons.

[Ashish Mani Tripathi]

Completely agree with you. 

[Kathy Hart]

Mine is with Logging Time on Jira tickets. 

It is great that you can do estimates for tickets, roll up the time from subtasks to stories, log time and burn down the estimate or edit the estimate if time used did not change the final outcome. 

HOWEVER, there is not a report feature anywhere that uses that logged time! Even the filter results are sketchy and not useful for anything. 

[Kathy Hart]

Automation: Counting Components in a Automation rule to judge when you are getting close to or have busted the limit with your rule. 

There is not a counter, and also, if you scroll down through the rule you created and count the components, it is meaningless. Apparently there are hidden components that get counted and can make you go over the limit without you being aware of them. 

[Ashish Mani Tripathi]

That's right, even I have the same complaint. If jira has functionality to log the time then why not have a gadget to report the same. Why we have to look for 3rd part add-on.

[Ashish Mani Tripathi]

Being a Jira admin, I want Jira fields to get sort quickly so that we can design a project. 

In Jira server, we had functionality to sort custom fields by its type. But in Jira cloud, we don't have it that is strange. How could you expect admins to go each page of custom fields to find suitable field with type to a project.

[Holly Scott]

One more, it'd be great to save a team-managed project's workflow as a template so it can be applied to other projects without having to recreate it repeatedly.

[Robin Stemmers]

Agreed. It would be nice if it worked like the automation where you can export and import it, without having to sign up to be a vendor.