-
Type:
Suggestion
-
Resolution: Won't Do
-
Environment:Java Version 1.6.0
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.6.0-b105
Java Runtime Java(TM) SE Runtime Environment
Java VM Java HotSpot(TM) Client VM
User Name SYSTEM
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.20
Database type mssql
Database JNDI address java:comp/env/jdbc/JiraDS
Database URL jdbc:jtds:sqlserver://localhost:1433/jiradb
Database version 09.00.3042
Database driver jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2Java Version 1.6.0 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.6.0-b105 Java Runtime Java(TM) SE Runtime Environment Java VM Java HotSpot(TM) Client VM User Name SYSTEM 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.20 Database type mssql Database JNDI address java:comp/env/jdbc/JiraDS Database URL jdbc:jtds: sqlserver://localhost:1433/jiradb Database version 09.00.3042 Database driver jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
When we resolve an issue, we want the Assignee field to select the reporter by default, but allow the resolver to select another user. Currently the Assignee field defaults to the currently assigned user, usually the resolver. This is never the correct value for this field during a Resolve transition.
When we reopen an issue, we want the Assignee field to select the last assigned user. I note there is already a request for this functionality.
Our plan is to install a Post Function that assigns the issue to the Reporter, and remove the Assignee field from the resolve screen. This is less than ideal. We have no simple solution for re-opened issues.
What I'd really like is some kind of pre-function that can alter values to be displayed on the web form without yet touching the underlying database. Seems like this would allow for a wide variety of customizable transition behaviors and resolve a lot of bugs in this database.
- is related to
-
JRASERVER-13768 Default values for fields during a transition
- Closed