Well, what I get from this are couple things, I'll start with the obvious one:
Our jira instance helpdesk is saying he doesnt have enough ram.
Whoever said that should be put in a corner for a week to think about what they did, find somebody else to talk to other than this person.
Once you find somebody who is not entirely incompetent, the first thing they will want is a HAR file. Since a HAR file may contain sensitive data, cookies and headers, it's best not to put it up here, but a competent admin will know what to do with it.
What the HAR file should prove is whether this is a network related issue or not - and this goes (most importantly) hand in hand with tomcat logs which the admin can check to see the response time for the user when they tried to transition an issue. In the logs, essentially they can see how long Jira took to respond to the transition request. If it's high - that indicates the problem is in Jira. If it's low (say, 3 seconds), and the user claims that request took minutes (confirmed by the HAR file) - then that would indicate network problems. There are a few extra things here and there but that's the gist of it, assuming that the rest of the userbase is not having problems.
The takeaway from this is that both HAR as well as tomcat logs will narrow down the location of the issue. If it's on the server, then the service team will need to investigate what's holding that request, if it's network (specifically by tomcat/lb logs having far lower duration than what the user experiences), then that of course gets complicated quite a lot.
Long story short is that we cannot tell you why that would be, I know for a fact transitions are not exactly the smoothest thing in Jira, but minutes are far too much, especially if you say that other users are fine, but only specific user(s) are affected. This on principle tells me it's something the users have in common. We'd need the logs, har files, all of which are typically sensitive, and perhaps even need to do some more stuff to the servers for extra details, so this is something that service team has to work on with you.
What I do find especially odd is the notion of a new laptop being the connection. If that were so (maybe some really, really trippy and terrible software on it?), I would assume you would see the problem elsewhere, not just workflow transitions.
In any case, the first point would be to find somebody who is actually competent enough to understand where to look and confirm whether this is a problem in Jira or not - and the RAM guy or gal is not the one.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.