New and Improved 3.13 Beta. Highlights: Shareable filters and dashboards and lots of other goodies. Any feedback can be raised as JIRA issues in the JIRA project.
Issue Details (XML | Word | Printable)

Key: JRA-8628
Type: Improvement Improvement
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Michael Calleja
Votes: 3
Watchers: 2
Operations

If you were logged in you would be able to see more operations.
JIRA

Ability to report on issues based on age

Created: 23/Nov/05 08:18 PM   Updated: 14/Nov/06 07:03 PM
Component/s: Reports
Affects Version/s: 3.4
Fix Version/s: None

Time Tracking:
Not Specified

Environment:
System Date Thursday, 24 Nov 2005
System Time 13:17:23
Java Version 1.5.0
Java Vendor Sun Microsystems Inc.
JVM Version 1.0
JVM Vendor Sun Microsystems Inc.
JVM Implementation Version 1.5.0-b64
Java Runtime Java(TM) 2 Runtime Environment, Standard Edition
Java VM Java HotSpot(TM) Client VM
User Name mxc
User Timezone Australia/Sydney
User Locale English (Australia)
System Encoding Cp1252
Operating System Windows XP 5.1
OS Architecture x86
Application Server Container Apache Tomcat/5.5.9
Database type mssql
Database JNDI address java:comp/env/jdbc/JiraDS

Java VM Memory Statistics
Total Memory 127 MB
Free Memory 92 MB
Used Memory 35 MB
Memory Graph
72 % Free (Force garbage collection)

JIRA Info
Uptime 7 minutes, 26 seconds
Edition Enterprise
Version 3.4.1
Build Number 107

Database Statistics
Issues 4490
Projects 46
Custom Fields 49
Workflows 4
Users 128
Groups 94

File Paths
Location of entityengine.xml file:/C:/Jira3.4/atlassian-jira-enterprise-3.4.1-standalone/atlassian-jira/WEB-INF/classes/entityengine.xml


Participants: Michael Calleja
Since last comment: 2 years, 40 weeks ago
Labels:


 Description  « Hide
We require the ability to Filter issues depending on the Priority and Age of an issue. For example
All Critical issues outstanding created more than 2 days ago
All High issues outstanding created more than 5 days ago

We would save this filter and create a mail subscription. This is necessary for us as part of our escalation path which we use to monitor outstanding client reported issues



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
There are no comments yet on this issue.