Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: None
-
Fix Version/s: 1.0
-
Component/s: None
-
Labels:
Description
When a user logs an activity (a meeting or call), the meeting/call has been completed. The status should therefore equal completed by default.
Though this is logical, some of the detail behavior doesn't make sense. If I log a call as unreachable, then it should remain an open issue until the call becomes completed. But the user can change from the default (completed) to unreachable.
One can assume that this behavior will extend to other activity types.
And I go back to a circular conclusion... all activity types should have a single default and the user should make a choice about changing that single default.
Scheduled doesn't make sense as that default, so I would suggest the default be "open" to keep consistent with the UI labels for open activities.
Attachments
Issue Links
Activity
Let's default status on Log a mtg, log a call to 'Completed' but NOT freeze the field - so user can change if needed.
was a bug introduced when i tweaked the template to include other parameters
The default field settings (e.g. status) for log is true vs. log is false is messed up, and the $log var value is no longer being assigned to smarty (shows as empty in smarty debug).