The display of bounty notices with custom text has been updated to preserve double line breaks and to highlight custom text in a more visible and consistent way.
Here is how it will look for single line bounty messages:
Here is how it will look for bounty messages that have multiple lines:
Each bounty message can have at most four paragraphs. Any ...
You'd flag the question; use other and explain why you think a moderator should look into the bounty. I recently flagged a bountied question with:
This is clearly off-topic, but I cannot VtC; can the bounty be removed and the question closed please?
and a moderator refunded the bounty and closed the question.
It doesn't matter if the bounty was started ...
Several times now I've really, really wanted to edit a bounty notice now for moderation purposes.
Today a bounty was flagged for using excessive emoji. The bounty was already well under way, and had attracted an answer that must've taken some work, so removing the bounty would be unfair to the answer-er competing for a 250 point bounty. We can't guarantee ...
You can enter 3000 characters when creating a bounty. Forcing all of that into a single paragraph is not useful.
Additionally, even small blocks of text can be clearer and easier to read if they are split up into paragraphs.
It is not yet added to the revision history but my earlier feature request to add this data to SEDE has been status-completed.
So until this gets added to the revision history you can now run this query
select pn.body as [Custom Comment]
, pt.Name as [Notice Type]
, pt.Body as [Reason]
The difference is in what you want the people answering and trying to get the bounty to focus on.
Do you simply want more answers? - use Draw attention.
Do you need authoritative references? use Authoritative reference needed.
Whatever you choose, the system treats the same way - it is just displaying a different message as the bounty message.
As Ashish said, the reasons for awarding a bounty may be different than the reasons for accepting an answer. So let's start with what's obvious: the reason an answer is accepted is usually because it is what solved the problem for the one who asked the question.
Also, as Ashish said, a bounty can be provided by someone other than the one who asked the ...
The display of bounty notices with custom text has been updated to preserve double line breaks, and to highlight custom text in a more visible and consistent way. This is only applying to double-line breaks. You can read more about it (and see screenshots) in this answer.
Taking SevenSidedDie's comment into account, if the reason for not allowing line breaks is for "distinctness between the bounty's fixed information lines and the optional message", an alternative could be to only allow single line-breaks.
This allows users to separate their bounty descriptions into sections, while keeping the user description as a single ...
As you mention, several questions request that the custom message be preserved. As of now, it is not preserved in the most natural location for it, the post's revision history. For example, this post definitely had a custom message (I wrote one) but the revision history shows only the category I selected:
No tooltips provide my text either.
The other ...
StackExchange questions tend to be very narrowed or specific because that is the way the system is designed, to give specific & thus, detailed answers to a practical scenario.
Now, imagine an answer that perfectly solves the OP's problem, but actually is a bit obfuscated solution which is not easily readable code, but it does the job perfectly. So, this ...