Bug 269247 - [New Journal] creates a new journal entry
Summary: [New Journal] creates a new journal entry
Status: RESOLVED UNMAINTAINED
Alias: None
Product: korganizer
Classification: Applications
Component: journalview (show other bugs)
Version: 4.4.10
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-23 17:45 UTC by Christopher Yeleighton
Modified: 2017-01-07 22:20 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Yeleighton 2011-03-23 17:45:51 UTC 
Version:           4.4.10 (using KDE 4.6.0) 
OS:                Linux

The button [New Journal] creates a new journal entry, not a new journal.

Reproducible: Always

Steps to Reproduce:
  1. Tell KOrganizer to create a new journal.

Actual Results:  
  1. KOrganizer creates a new journal entry.

Expected Results:  
  1. Let KOrganizer create a new journal.

OS: Linux (x86_64) release 2.6.37.1-1.2-desktop
Compiler: gcc
Comment 1 Sergio Martins 2011-03-23 19:02:17 UTC 
What's the difference between "Journal entry" and "Journal" ?

Please clarify these two concepts.
Comment 2 Christopher Yeleighton 2011-03-24 08:20:56 UTC 
Adding Journal Entries
<URL: help:/korganizer/chapter-views-and-filters.html#journal-view >
Comment 3 Sergio Martins 2011-03-24 12:29:23 UTC 
Journal entry and journal are the same thing.
Comment 4 Christopher Yeleighton 2011-03-24 12:53:31 UTC 
Exactly like a dictionary entry and a dictionary.
Comment 5 Denis Kurz 2016-09-24 18:42:22 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of korganizer (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 6 Denis Kurz 2017-01-07 22:20:14 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.