Details
-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
3.5.3
-
System Date Monday, 31 Jul 2006
System Time 14:36:27
Current Working Directory C:\jira360\atlassian-jira-enterprise-3.6-standalone\bin
Java Version 1.5.0_05
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.5.0_05-b05
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Client VM
User Name sdavies
User Timezone America/Los_Angeles
User Locale English (United States)
System Encoding Cp1252
Operating System Windows 2003 5.2
OS Architecture x86
Application Server Container Apache Tomcat/5.5.9
Database type mssql
Database JNDI address java:comp/env/jdbc/JiraDS
Database version 08.00.2039
Database driver jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2System Date Monday, 31 Jul 2006 System Time 14:36:27 Current Working Directory C:\jira360\atlassian-jira-enterprise-3.6-standalone\bin Java Version 1.5.0_05 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.5.0_05-b05 Java Runtime Java(TM) 2 Runtime Environment, Standard Edition Java VM Java HotSpot(TM) Client VM User Name sdavies User Timezone America/Los_Angeles User Locale English (United States) System Encoding Cp1252 Operating System Windows 2003 5.2 OS Architecture x86 Application Server Container Apache Tomcat/5.5.9 Database type mssql Database JNDI address java:comp/env/jdbc/JiraDS Database version 08.00.2039 Database driver jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2
-
3.05
-
Severity 2 - Major
-
Description
We have configured our edit issue screens to remove, amongst other things, the reporter field to prevent someone from changing the reporter. Today, one of our developers, by mistake, did a bulk edit operation and managed to hit the reporter instead of the assignee field.
Given the amount of grief this caused today, this is a critical issue.
One of two things would be fine...
1. Make the bulk edit screen always be consistent with the single issue edit screen in terms of fields displayed
2. Or...slightly more flexible...provide for a seperate bulk edit screen that can be modified using the screen editor
Attachments
Issue Links
- relates to
-
JRASERVER-11229 Bulk Edit allows change of issue type without regard for the associated workflow - thereby creating orphaned issues
- Closed