[ALF-1025] After canceling site creation fields aren't cleared Created: 22-Oct-09  Updated: 31-Aug-16  Resolved: 17-Jul-14

Status: Closed
Project: Alfresco
Component/s: ZZ_Archive
Affects Version/s: 3.1 Enterprise, 3.5 (Team)
Fix Version/s: None

Type: Bug Priority: Minor
Reporter: Alfresco QA Team (Inactive) Assignee: Closed Issues
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Alfresco 3.1.2 EE build 362 Stack 1 , RHEL 5.1 x64, MySQL 5.1.30, Tomcat 6.0.18, JDK 6u16 x64, Kerberos, Windows XP, IE 6


Testcase ID:

Share-82

Date of First Response:

 Description   

Steps to reproduce:
1. Click "Create Site" link;
2. Specify Name, URL, Description and click "Cancel" button;
3. Click "Create Site" link again -> the fields are filled with previously added info;

Olgadu



 Comments   
Comment by Erik Winlof [X] (Inactive) [ 27-Oct-09 ]

Fixed since revision 17169

Comment by Alfresco QA Team (Inactive) [ 28-Oct-09 ]

The issue is reproduced on Alfresco 3.1.2 EE build 362 - Stack 2 , Windows 2008 Ent SP1 x64, MSSQL 2005 SP2, JBoss 4.2.3, JDK 6u16 x64, RMICacheManager, NTLM passthru, Windows Vista, IE7

Comment by Steve Rigby [X] (Inactive) [ 02-Nov-09 ]

For retest in b205 or later

Comment by Alfresco QA Team (Inactive) [ 03-Nov-09 ]

Successfully validated on Alfresco 3.2 EE build 194 RHEL 5.1 x64, Tomcat 6.0.18, Mysql 5.1.30, JDK 6u14 x64, Windows XP, FF3

Comment by Alfresco QA Team (Inactive) [ 27-Nov-09 ]

Have to reopen as the issue is reproduced again on Alfresco 3.2 EE build 267 (Stack 2: Windows 2008 SP1 x64, Oracle 10g 10.2.0.3, JBoss 5.1.0 GA, JDK 6u16, NTLM, Windows Vista, IE 7)

Comment by Steve Rigby [X] (Inactive) [ 02-Dec-09 ]

merge issue?

Comment by Alfresco QA Team (Inactive) [ 21-Mar-11 ]

Reproduced on Alfresco Enterprise v3.5.0 (102), Windows 2008: Tomcat, PostgreSQL, Java 6 (all installer deployed) Client: Windows 7, Firefox 3.6.13

Comment by Steve Rigby [X] (Inactive) [ 30-Mar-11 ]

Transitioned 'reopened' bugs to the 'open' state.

Comment by Will Taylor [X] (Inactive) [ 17-Jul-14 ]

This issue has been re-triaged and determined as “Won’t Fix” and Closed.
Many factors were considered in this decision, among which is the need to correctly prioritise the work of the Engineering team and be clear with those issues that are not going to be resolved.

Generated at Tue May 18 06:47:57 BST 2021 using Jira 7.13.15#713015-sha1:7c5ddd2c3e1709974ae9c48c17df8edd3919fe2c.