• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Jira 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.

      I have noticed several issues in the database across several projects that are related to the browsers "Back" button. That is because data and state information is not saved prior to actual user execution. Any user inputed data, queries, attachment selections, etc will all be destroyed if the back button is pressed. This is extremely frustrating for me because I have a mouse with fwd. and back buttons near my thumb, and I frequently press them accidentally. I am new to Jira, but have alrady had about 3 incidents that have caused me to loose detailed bug reports. This costs the company money, and wasted time every incident. It just seems prudent to prevent this from occuring by either saving the data in a temprorary location, or by warning the user if data has been submitted, and the back button is pressed. There has got to be a way to either prevent this, or reduce the risk by warning users before it happens. This issue is too frequently submitted in Jira, and Confluence to ignore.

          Form Name

            [JRASERVER-10858] Back Button Destroys Data

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3059205 ] New: JAC Suggestion Workflow 3 [ 3686632 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2616627 ] New: JAC Suggestion Workflow [ 3059205 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2584548 ] New: Confluence Workflow - Public Facing v4 [ 2616627 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361400 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2584548 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2128976 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2361400 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091942 ] New: JIRA Bug Workflow w Kanban v6 [ 2128976 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 879343 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2091942 ]
            Oswaldo Hernandez (Inactive) made changes -
            Component/s Original: Web interface [ 10126 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 709529 ] New: JIRA Bug Workflow w Kanban v6 [ 879343 ]
            Roy Krishna (Inactive) made changes -
            Backlog Order (Obsolete) Original: 55880000000
            Bugmaster Rank (Obsolete) Original: 79530000000
            JIRA Support Rank (Obsolete) Original: 88960000000
            Studio Rank (Obsolete) Original: 82090000000
            Support Rank (Obsolete) Original: 82090000000
            Workflow Original: PM Feature Request Workflow [ 221559 ] New: JIRA PM Feature Request Workflow v2 [ 709529 ]
            Issue Type Original: New Feature [ 2 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]

              Unassigned Unassigned
              c5b13e874029 Byron L. Spires
              Votes:
              6 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: