History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: JRA-7394
Type: New Feature New Feature
Status: Resolved Resolved
Resolution: Duplicate
Priority: Minor Minor
Assignee: Unassigned
Reporter: Hartono Adji
Votes: 0
Watchers: 0
Operations

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

Custom Fields filter request for Security Level parameter

Created: 21/Jul/05 03:11 AM   Updated: 22/Jul/05 03:23 AM
Component/s: Custom Fields (new types)
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Duplicate
 

Participants: Hartono Adji and Jeff Turner [Atlassian]
Since last comment: 156 weeks, 2 days ago
Resolution Date: 22/Jul/05 03:23 AM
Labels:


 Description  « Hide
Victor Rodrigues/CLTD/COH 21-07-2005 16:47
To Hartono Adji/CLTD/COH@COH_NOTES
cc
Subject Re: security level

Unfortunately I cannot do anything about this. I suggest you submit a feature request to Atlassian http://jira.atlassian.com/default.jsp?clicked=footer.

----------------------------------------------------------------------------
Victor Rodrigues
Audiological Software Manager
Cochlear Ltd, 14 Mars Road
Lane Cove, NSW, 2066
Australia
Tel: +61 2 9428 6303
Mobile: +61 438 456 947
----------------------------------------------------------------------------

Hartono Adji/CLTD/COH 21/07/2005 04:04 PM
To Victor Rodrigues/CLTD/COH@COH_NOTES
cc
Subject security level

Hi Victor,

I tried to search in JIRA for Test Observation issue. I found that 'Find Issue' facility in JIRA does not have this filter. The Custom Fields only display Severity its bottom options.

It would be good if we can have this custom fields, but it is up to you whether it will require too much work or not to provide this custom field.

Thanks,
Hartono



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Jeff Turner [Atlassian] - 22/Jul/05 03:23 AM
Victor is correct - being able to search by security level is not yet possible in JIRA, but is a requested feature:

http://jira.atlassian.com/browse/JRA-2925