ACSP Suggestion 2013.29: Improve ARIN Online Form Time-Out Behavior

Author: Owen DeLong

Submitted On: 06 November 2013

Suggestion

Bug Report: Timed-out ticket forms are not graceful.

To reproduce:

  1. Log into ARIN Online
  2. Track Tickets
  3. Select an open ticket and bring up its details.
  4. Walk away from the browser long enough for the session to time out.
  5. Come back, the ticket is still on the screen and no asynchronous notification of the session timeout is presented.
  6. Not realizing that the session has timed out, enter comments for the ticket into the text box and press submit.

Expected result: A) The comments are accepted and then I am logged out of the ticket system for inactivity, or, B) the comments are buffered and I must log into ARIN online again to validate their submission

Actual result: I am dumped back to the logged-out state, all of my text is lost, and I have to log in, find the ticket, and retype my comments from scratch.

 

Timeframe: Immediate

Suggestion Information

Status: Closed

Updated: 23 September 2019

Suggestion Tracking

ARIN Comment

23 September 2019

Thank you for your suggestion, numbered 2013.29 on confirmed receipt, asking that we extend the time-out behavior for forms in ARIN Online. We have completed this work when we deployed stateless architecture on 2 March 2019.

Because this work has been completed, we are closing your suggestion. Thank you for your participation in the ARIN Consultation and Suggestion Process. We apologize for the delay in notification that this work was completed.

ARIN Comment

10 April 2018

The effort to satisfy this suggestion is currently part of our 2018 Work Plan. It will be closed upon completion.

ARIN Comment

28 March 2014

Implementation Estimate: This will take 2 person months.

Please note that these are good-faith, general estimates to include development, testing, and implementation; as such they are subject to change.

ARIN Comment

18 November 2013

Thank you for your suggestion, which was numbered 2013.29 upon receipt. This suggestion - specifically the behavior described in result A, is reasonable and we plan on adding it to the list of outstanding projects awaiting prioritization found at: https://www.arin.net/features/#tbd.

Please note that we will be consulting the ARIN community to help access prioritization of improvements of existing systems, as well as additional services that the community desires. This will be fed back into ARIN's planning process for scheduling development resources to complete the suggestion.

ARIN will keep this suggestion open until it is completed.