For some reason I never noticed your Comment #2 from 06-Mar, and just now saw your #3.

Interestingly though, the email that I received as a copy of your Comment #3 had the customized Subject field that I had set up.

So, given that, is it possible that what you meant by "the feature seems to only be active for your own postings" really means that "the feature seems to be active only for tickets for which you are the originator"? (By "originator" I mean the user listed in the "Submitted By" field.)

If this is the case, then I agree with your inclination to disable the feature, since in its present state it doesn't seem to behave per user expectation, and the way that it does behave -- providing the customized Subject line only for tickets which one originated -- doesn't seem to accomplish anything useful. It's often the case that a user contributes many comments to a ticket that they did not originate

This "usefulness" assessment is based on the assumption that the intent of the feature was to allow structuring the Subject line so that it could be used for mail filtering purposes at the destination host. But if it works only for self-originated postings and not for postings originated by others, then it would seem not to serve this purpose very well.

In short, I'm in agreement with you that it's probably better to disable it than leave it and have others waste their time setting it up only to find it doesn't behave as they probably expected.

This is a feature that I didn't know existed until your report.  I turned it on for me so that I could test the feature before commenting upon it.  And then rather forgot about it for a while.  Then messages started coming through with the subject header and I remembered it.

As far as I can see the feature seems to only be active for your own postings.  Other people's postings do not have the custom header.  By my own do.  I think that must be just the way it works.  Probably it was only partially implemented in the web site code.

The feature seems of limited utility.  But it seems to do what it seems to do.  There hasn't been active development of Savannah for a while.  It has been in a deep maintanence mode only.  There isn't really anyone to comment upon the feature or to implement changes to it.

If this is something you felt like contributing then patches would always be welcome.  But otherwise quite frankly I don't think it would get improved to handle that better otherwise.  Since so far no one has volunteered to own the ticket myself included.

While this does seem like incomplete implementation because it doesn't break the system in general and most people won't even notice I am downgrading the severity from important.

In the account configuration page

   https://savannah.gnu.org/my/admin/change_notifications.php

there's an option ("Subject Line") to allow the user to specify a custom Subject line for messages. It doesn't seem to have any effect; I changed it several days ago to a custom value, yet all received messages still have the standard header.