Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-27272

Implement checkbox that allows users to ask for longer session time limit or no session time limit

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Per Web Content Accessibility Guidelines (WCAG), we could implement a checkbox that allows users the option for more time before their session times out when editing page content ("technique" page).

            [CONFSERVER-27272] Implement checkbox that allows users to ask for longer session time limit or no session time limit

            Sherif Mansour added a comment -

            rrollins it was closed because there was no real context provided to the ticket and we wouldn't implement another checkbox...

            In your specific issue.. do you know how long you left your page for? more than 24 hours? If you hit save, it looked like your work was gone, but it would have still been in the form... so if you refreshed once it was back up that would have submitted it..

            Either way, I don't think this how we would fix your problem we would:
            1. Improve the editor reliability so you can't "Save" if the server is not up (so you don't corner yourself) (CONF-30734)
            2. Extend the session timeout. At the moment this can be done manually, but I think maybe our default (https://confluence.atlassian.com/pages/viewpage.action?pageId=126910597) is far too low. (CONF-30773)

            What I've done is raised a couple of issues for both of these that you might watch.

            Sherif Mansour added a comment - rrollins it was closed because there was no real context provided to the ticket and we wouldn't implement another checkbox... In your specific issue.. do you know how long you left your page for? more than 24 hours? If you hit save, it looked like your work was gone, but it would have still been in the form... so if you refreshed once it was back up that would have submitted it.. Either way, I don't think this how we would fix your problem we would: 1. Improve the editor reliability so you can't "Save" if the server is not up (so you don't corner yourself) ( CONF-30734 ) 2. Extend the session timeout. At the moment this can be done manually, but I think maybe our default ( https://confluence.atlassian.com/pages/viewpage.action?pageId=126910597 ) is far too low. ( CONF-30773 ) What I've done is raised a couple of issues for both of these that you might watch.

            Russ Rollins added a comment -

            Just curious as to why this was immediately closed? I experienced a timeout out on a Monday, due to a some editing I started before the weekend, and lost all of the changes I made. Once the login screen intercepted by save, the error indicated an expired security token and recommended a re-submission. When I re-submitted, via refresh, all my work was gone.

            I'm currently evaluating Confluence for a company roll-out and this behavior concerns me. Hence my search that led me to this ticket.

            Russ Rollins added a comment - Just curious as to why this was immediately closed? I experienced a timeout out on a Monday, due to a some editing I started before the weekend, and lost all of the changes I made. Once the login screen intercepted by save , the error indicated an expired security token and recommended a re-submission. When I re-submitted, via refresh, all my work was gone. I'm currently evaluating Confluence for a company roll-out and this behavior concerns me. Hence my search that led me to this ticket.

              smansour Sherif Mansour
              alaskowski Adam Laskowski (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: