You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Martin von Gagern (JIRA)" <ji...@apache.org> on 2008/11/21 14:50:44 UTC
[jira] Created: (INFRA-1799) Avoid losing bug descriptions to
logout
Avoid losing bug descriptions to logout
---------------------------------------
Key: INFRA-1799
URL: https://issues.apache.org/jira/browse/INFRA-1799
Project: Infrastructure
Issue Type: Wish
Security Level: public (Regular issues)
Components: JIRA
Environment: Linux, Firefox 3.0.4
Reporter: Martin von Gagern
I just spent an estimated 1.5h writing a detailed bug report for an ASF project. When I started typing, I was logged into JIRA. When I submitted the report, JIRA informed me that anonymous users weren't allowed to create issue reports, and that I would have to log in. When I pressed "back", I got an empty issue form. The text of my bug report was lost. At that moment I had a heartfelt scream, before I started typing the report over again, slightly annoyed, with less detail and less quality in my writing. I used another browser tab to log in just before submitting the request, and made sure to copy the text to the clipboard, just to be safe.
I consider this an issue you should fix in order to get the most from community contributions. Possible approaches, may be combined:
1. Drastically increase time before automatic logouts. I guess at least that this is what happened to me, as I doubt my IP has changed.
2. Display a form to provide input credentials and store form data in hidden elements, so that the users can log in and resubmit their report in one go.
3. Ensure navigation doesn't destroy form contents. Usually Firefox can go back in history and also restore form data, but on JIRA that doesn't seem to work.
Of course it might be that some of these issues would have to be addressed by Atlassian. If so, I guess the ASF is the direct customer of Atlassian and thus best suited to forward appropriate requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (INFRA-1799) Avoid losing bug descriptions to logout
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Henri Yandell closed INFRA-1799.
--------------------------------
Resolution: Later
It's reported to Atlassian as:
http://jira.atlassian.com/browse/JRA-14031
I've voted for it there.
> Avoid losing bug descriptions to logout
> ---------------------------------------
>
> Key: INFRA-1799
> URL: https://issues.apache.org/jira/browse/INFRA-1799
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Environment: Linux, Firefox 3.0.4
> Reporter: Martin von Gagern
> Assignee: Henri Yandell
>
> I just spent an estimated 1.5h writing a detailed bug report for an ASF project. When I started typing, I was logged into JIRA. When I submitted the report, JIRA informed me that anonymous users weren't allowed to create issue reports, and that I would have to log in. When I pressed "back", I got an empty issue form. The text of my bug report was lost. At that moment I had a heartfelt scream, before I started typing the report over again, slightly annoyed, with less detail and less quality in my writing. I used another browser tab to log in just before submitting the request, and made sure to copy the text to the clipboard, just to be safe.
> I consider this an issue you should fix in order to get the most from community contributions. Possible approaches, may be combined:
> 1. Drastically increase time before automatic logouts. I guess at least that this is what happened to me, as I doubt my IP has changed.
> 2. Display a form to provide input credentials and store form data in hidden elements, so that the users can log in and resubmit their report in one go.
> 3. Ensure navigation doesn't destroy form contents. Usually Firefox can go back in history and also restore form data, but on JIRA that doesn't seem to work.
> Of course it might be that some of these issues would have to be addressed by Atlassian. If so, I guess the ASF is the direct customer of Atlassian and thus best suited to forward appropriate requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (INFRA-1799) Avoid losing bug descriptions to
logout
Posted by "#asfinfra IRC Bot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-1799?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
#asfinfra IRC Bot updated INFRA-1799:
-------------------------------------
Assignee: Henri Yandell
> Avoid losing bug descriptions to logout
> ---------------------------------------
>
> Key: INFRA-1799
> URL: https://issues.apache.org/jira/browse/INFRA-1799
> Project: Infrastructure
> Issue Type: Wish
> Security Level: public(Regular issues)
> Components: JIRA
> Environment: Linux, Firefox 3.0.4
> Reporter: Martin von Gagern
> Assignee: Henri Yandell
>
> I just spent an estimated 1.5h writing a detailed bug report for an ASF project. When I started typing, I was logged into JIRA. When I submitted the report, JIRA informed me that anonymous users weren't allowed to create issue reports, and that I would have to log in. When I pressed "back", I got an empty issue form. The text of my bug report was lost. At that moment I had a heartfelt scream, before I started typing the report over again, slightly annoyed, with less detail and less quality in my writing. I used another browser tab to log in just before submitting the request, and made sure to copy the text to the clipboard, just to be safe.
> I consider this an issue you should fix in order to get the most from community contributions. Possible approaches, may be combined:
> 1. Drastically increase time before automatic logouts. I guess at least that this is what happened to me, as I doubt my IP has changed.
> 2. Display a form to provide input credentials and store form data in hidden elements, so that the users can log in and resubmit their report in one go.
> 3. Ensure navigation doesn't destroy form contents. Usually Firefox can go back in history and also restore form data, but on JIRA that doesn't seem to work.
> Of course it might be that some of these issues would have to be addressed by Atlassian. If so, I guess the ASF is the direct customer of Atlassian and thus best suited to forward appropriate requests.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.