| Key: |
JRA-2303
|
| Type: |
Improvement
|
| Status: |
Resolved
|
| Resolution: |
Duplicate
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
Lars Kühne
|
| Votes: |
3
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
JIRA
Created: 08/Sep/03 01:44 AM
Updated: 26/Aug/04 01:07 AM
|
|
| Component/s: |
Workflow
|
| Affects Version/s: |
2.2.1 Pro
|
| Fix Version/s: |
None
|
|
|
Issue Links:
|
Duplicate
|
|
This issue duplicates:
|
|
|
JRA-1744 "Log work done" as a MANDATORY field when resolving issues
|
|
|
|
|
|
|
|
| Participants: |
Lars Kühne
|
| Since last comment: |
254 weeks, 4 days ago
|
| Resolution Date: |
26/Aug/04 01:07 AM
|
| Labels: |
|
For timetracking to work effectively, the underlying data must be consistent. This means that developers have to log their work for timetracking reports to be meaningful.
Request: prevent resolving an issue if timetracking is enabled, work logged == 0 and resolution != duplicate, so developers are forced to log their work.
|
|
Description
|
For timetracking to work effectively, the underlying data must be consistent. This means that developers have to log their work for timetracking reports to be meaningful.
Request: prevent resolving an issue if timetracking is enabled, work logged == 0 and resolution != duplicate, so developers are forced to log their work. |
Show » |
| There are no comments yet on this issue.
|
|
