Details
-
Suggestion
-
Resolution: Low Engagement
-
System Info
System Date Thursday, 17 Aug 2006
System Time 09:49:56
Current Working Directory /tracker362/atlassian-jira-enterprise-3.6.2-standalone/bin
Java Version 1.4.2_05
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.4.2_05-b04
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Client VM
User Name root
User Timezone Australia/Sydney
User Locale English (Australia)
System Encoding UTF-8
Operating System Linux 2.4.20-8smp
OS Architecture i386
Application Server Container Apache Tomcat/5.5.9
Database type mssql
Database JNDI address java:comp/env/jdbc/JiraDS
Database version 08.00.0760
Database driver jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2
Java VM Memory Statistics
Total Memory 254 MB
Free Memory 62 MB
Used Memory 192 MB
Memory Graph
[Used Memory ( 76 %)] [Free Memory ( 24 %)]
24 % Free (Force garbage collection)
JIRA Info
Uptime 1 day, 19 hours, 22 minutes, 15 seconds
Edition Enterprise
Version 3.6.2
Build Number 156
Atlassian Partner
Database Statistics
Issues 9709
Projects 57
Custom Fields 57
Workflows 9
Users 178
Groups 88
File Paths
Location of entityengine.xml file:/tracker362/atlassian-jira-enterprise-3.6.2-standalone/atlassian-jira/WEB-INF/classes/entityengine.xml
Location of atlassian-jira.log file:/tracker362/atlassian-jira-enterprise-3.6.2-standalone/bin/atlassian-jira.logSystem Info System Date Thursday, 17 Aug 2006 System Time 09:49:56 Current Working Directory /tracker362/atlassian-jira-enterprise-3.6.2-standalone/bin Java Version 1.4.2_05 Java Vendor Sun Microsystems Inc. JVM Version 1.0 JVM Vendor Sun Microsystems Inc. JVM Implementation Version 1.4.2_05-b04 Java Runtime Java(TM) 2 Runtime Environment, Standard Edition Java VM Java HotSpot(TM) Client VM User Name root User Timezone Australia/Sydney User Locale English (Australia) System Encoding UTF-8 Operating System Linux 2.4.20-8smp OS Architecture i386 Application Server Container Apache Tomcat/5.5.9 Database type mssql Database JNDI address java:comp/env/jdbc/JiraDS Database version 08.00.0760 Database driver jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2 Java VM Memory Statistics Total Memory 254 MB Free Memory 62 MB Used Memory 192 MB Memory Graph [Used Memory ( 76 %)] [Free Memory ( 24 %)] 24 % Free (Force garbage collection) JIRA Info Uptime 1 day, 19 hours, 22 minutes, 15 seconds Edition Enterprise Version 3.6.2 Build Number 156 Atlassian Partner Database Statistics Issues 9709 Projects 57 Custom Fields 57 Workflows 9 Users 178 Groups 88 File Paths Location of entityengine.xml file:/tracker362/atlassian-jira-enterprise-3.6.2-standalone/atlassian-jira/WEB-INF/classes/entityengine.xml Location of atlassian-jira.log file:/tracker362/atlassian-jira-enterprise-3.6.2-standalone/bin/atlassian-jira.log
-
0
-
15
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
We require the ability to have an issue automatically assigned to a user based on the value of custom field. It would be useful to define this via the workflow operations so that if the custom field is left blank, or multiple selection made, the issue can be assigned to a default assignee such as the Project lead, or the component leads.
This needs to part of Jira so that we can safely take all the upgrades tha Jira supply - it is not an option for us to implement the code provided on Jira Extension site
Attachments
Issue Links
- is related to
-
- Gathering Interest
