-
Type:
Bug
-
Resolution: Duplicate
-
Priority:
Low
-
None
-
Affects Version/s: 3.8.1
-
Component/s: Issue - Fields
-
Environment:
System Date Wednesday, 08 Aug 2007
System Time 21:57:02
Current Working Directory /
Java Version 1.6.0_01
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.6.0_01-b06
Java Runtime Java(TM) SE Runtime Environment
Java VM Java HotSpot(TM) Client VM
User Timezone Europe/Helsinki
User Locale English (United States)
System Encoding UTF-8
Operating System Linux 2.6.9-55.EL
OS Architecture i386
Application Server Container Apache Tomcat/5.5.23
Database type mysql
Database JNDI address java:comp/env/jdbc/JiraDS
Database URL jdbc:mysql://localhost/jiradb?autoReconnect=true&useUnicode=true&characterEncoding=UTF8
Database version 4.1.20
Database driver MySQL-AB JDBC Driver mysql-connector-java-3.1.12 ( $Date: 2005-11-17 15:53:48 +0100 (Thu, 17 Nov 2005) $, $Revision$ )
External user management OFF
Uptime 12 days, 11 hours, 33 minutes, 42 seconds
Edition Enterprise
Version 3.8.1
Build Number 210
Atlassian Partner
Installation Type EAR / WAR
Server ID A5XN-6VY4-7BU5-ZLKMSystem Date Wednesday, 08 Aug 2007 System Time 21:57:02 Current Working Directory / Java Version 1.6.0_01 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.6.0_01-b06 Java Runtime Java(TM) SE Runtime Environment Java VM Java HotSpot(TM) Client VM User Timezone Europe/Helsinki User Locale English (United States) System Encoding UTF-8 Operating System Linux 2.6.9-55.EL OS Architecture i386 Application Server Container Apache Tomcat/5.5.23 Database type mysql Database JNDI address java:comp/env/jdbc/JiraDS Database URL jdbc:mysql://localhost/jiradb?autoReconnect=true&useUnicode=true&characterEncoding=UTF8 Database version 4.1.20 Database driver MySQL-AB JDBC Driver mysql-connector-java-3.1.12 ( $Date: 2005-11-17 15:53:48 +0100 (Thu, 17 Nov 2005) $, $Revision$ ) External user management OFF Uptime 12 days, 11 hours, 33 minutes, 42 seconds Edition Enterprise Version 3.8.1 Build Number 210 Atlassian Partner Installation Type EAR / WAR Server ID A5XN-6VY4-7BU5-ZLKM
-
3.08
When changing the issue type to another that has new custom fields, the 4-step Move-procedure works otherwise great, but on the 4. Confirmation step JIRA does not show the new values that were entered in the 3. step.
Still, the values are set when I click "Move" – they just don't show up in the confirmation step like they should.
- duplicates
-
-
- Closed
-
