Issue Details (XML | Word | Printable)

Key: JRA-2558
Type: Improvement Improvement
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: Owen Fellows
Votes: 5
Watchers: 2
Operations

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

Minimum time periods are not configurable

Created: 30/Oct/03 05:24 PM   Updated: 13/Mar/08 10:02 PM
Component/s: Time Tracking
Affects Version/s: 2.5 BETA
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Reference
 

Participants: Geoffrey Wiseman and Owen Fellows
Since last comment: 3 years, 7 weeks, 6 days ago
Labels:


 Description  « Hide
When using the time tracking, the default if no descriptor is entered is minutes. We don't track anything in minutes. The smallest meaningful measure is hour. Is there any way to make the default hour? Better yet, is there any way to completely remove the ability to enter values in minutes?

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Geoffrey Wiseman added a comment - 18/Aug/05 12:57 PM
Alternately, if it's simpler, I'd be happy enough to have JIRA enforce that you must put in a suffix, so that if I accidentally put in '3' meaning '3 days', it'll give me an error that forces me to choose between 3m, 3d, 3h, etc. The biggest problem here is the potential for accidental (and, for our purposes, tiny) estimates and work logs that may or may not get noticed.