We all are aware that JIRA times out after 5 hours and asks you to login again if the page is left inactive for more than 5 hours(ver 5.0.2)
The bug I want to report is, say if you have an issue open on your screen, then after 5 hours you come back to the issue and press add comment, the system allows you to add a comment but when you press submit thats when the time out logic gets triggered.
I feel it is a bug with the software as the time out logic should have been triggered right when i press add comment and the system should not have allowed me to enter comment in the first place.
DO we have this bug already registered with JIRA? If not, i will log one.
Is there any workaround to this bug.?
I'm not sure that's directly a bug in Jira, as it applies to all sorts of web based software.
The session times out on the server side. How does the client you've left open know that this has happened? It can't until the next time it tries to contact the server, which is when you press "commit comment". You could try adding some batch of scripting to tell the client to maintain a timer and do something after a certain time (e.g. close the browser window, or jump back to the login screen), but it's a lot of work, for little reward.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs