Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,464,242
Community Members
 
Community Events
176
Community Groups

Issues duplicated randomly with a chance of ~ 1% - Chrome repeats POST Request

Edited

Hey everbody,

im just chasing a very strange phenomenon:

We have two client machines where users create a lot of issues per day (100-250 per day).

The issue creation takes quite some time as there are a lot of post functions in the workflow and the server is under high load from time to time, issue creation is usually taking ~15 seconds, but it can also take a minute.

For their use case we send the users right to the /secure/CreateIssueDetails.jspa page (instead of using the "overlay mode you get when you hit the create button.)

Now in about 1% of all issues created the issue is created twice with identical data.
In one case even 3 issues were created instead of one.

I checked the access-logs and i can see the POST request repeating about 15 seconds apart.
I have interviewed the guys working on the machines today and the both swear they didnt double click the create button,  hit enter or did anything else than just waiting for the request to complete

On these two machines the users recently switched from using firefox to using chrome because Jira for some unknown reason started to run significantly slow in Firefox, the issue has never occurred before they switched to chrome.

The Jira Instance is an outdated 7.13 instance which we are currently updating on a test system, but i would rather fix the problem on the old system before we upgrade the production system because the update is currently blocked due to some issues with apps.

Speaking of apps there are quite a few apps on the instance, the ones that add fields or code to the issue create page are Dynamic Forms, Script Runner Behaviours, Stagil Asset Releations. Another app that generates output in the browser console are SimpleTasks

Has anybody experienced something similar?

So far i avoided the effort to check if its reproducible on another system, i see myself creating 100 issues...

kind regards

Jens

 

2 answers

1 accepted

0 votes
Answer accepted

It only occurrs when the create screen is open in a separate Tab

https://jira.atlassian.com/browse/JRASERVER-37267

This is a know bug, open since 2014, minor serverity and only 50 votes.

So my guess is this will never be fixed at all.

Im wondering: as this bug is in the jira server project, will it automatically be closed when server maintenance expires or will it continue to exist as a data center bug?

The reason why we open the create screen in a new tab is because we can then prefill project and issuetype (and a  select field) with URL parameters:

/secure/CreateIssueDetails!init.jspa?pid=10400&issuetype=10414&summary=...&customfield_11871=11475

 Im asking Atlassian support if theres a way to prefill those when using the "overlay" create screen.

Charlie Misonne Community Leader Sep 06, 2021

Hi Jens,

Thanks for the update! I'm glad you found the bug report because I didn't.

The bug likely exists in Data Center as well I'm afraid.

Yeah i saw some people mentioning DC in the comments

1 vote
Charlie Misonne Community Leader Sep 02, 2021

That's odd and not something I have seen before in Jira. My first thought was users hitting the button twice when the creation is not quick enough too. But if those duplicate requests are always exactly 15s apart it doesn't sound like a user interaction

  1. Have you tried this yourself? Are you able to hit the create button twice?
    In decent UI desing a button should be disabled after it has been hit. But perhaps it is not the case for Jira 7.13
  2. Are those clients running recent versions of chrome? Perhaps you can find a related bug on https://bugs.chromium.org/p/chromium/issues/list
  3. Let them use another (not chromium based) browser on those clients to exclude any browser bugs
  4. Search jira.atlassian.com  for any related bugs (I couldn't find any) or the issue trackers of the plugins you are using (if they have one)

Hi Charlie, thanks for putting though in this.

1. i tried clicking a lot and in the chrome dev tools it looks like this:
sir-click-a-lot.PNG
The request get cancelled but they are processed anyway, i just deleted 46 issues.

This also happens in Jira 8.16 under Chrome.

3. We switched to the Vivaldi Browser to work around another browser issue we are having on these exact two machines and we'll monitor if the problem prevails

Hi Charlie,

found the bug ticket in JAC (see my other answer)

thank you!

Like Charlie Misonne likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events