If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Draft loses star mark when saving after an edit

NEW
Unassigned

Status

Thunderbird
Message Compose Window
--
minor
9 years ago
7 years ago

People

(Reporter: Bugzilla, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1b3) Gecko/20090305 Firefox/3.1b3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; sv-SE; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2

A draft, already saved and Marked with a star, loses that star if I open the draft, edit it and save it again. This bug was also in Thunderbird 2.

Reproducible: Always

Steps to Reproduce:
1. Save a draft
2. Mark it with a star
3. Open the draft in edit mode, change something in the message
4. Save the draft

Actual Results:  
Now the Star (mark) is gone! :(

Expected Results:  
The Star (mark) should still be there.
confirmed. but I wonder what is your use case?
do you keep a gazillion drafts like i do?

edit as new keeps starred.
edit and don't save keeps starred.
Severity: normal → minor
Summary: Draft loses "Mark" when saving after an edit → Draft loses star "Mark" when saving after an edit

Updated

9 years ago
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: x86 → All
Summary: Draft loses star "Mark" when saving after an edit → Draft loses star mark when saving after an edit

Comment 2

7 years ago
It is also loosing TAGS put on a draft message after sending the message.

Use case is following: I want to mark "messages I'm waiting an answer for" with a tag (like "Expect Answer"), when composing the message. The TagToolbar extension would be very handy to do that.
Or whatever other tag to classify the message I'm sending.

On TB3.1RC2

Comment 3

7 years ago
Sorry, ignore my previous comment here, I filed it against the wrong bug :(
(should have been bug 497105).
You need to log in before you can comment on or make changes to this bug.