This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 218478 - {message} keyword from Issue Tracker template is empty
Summary: {message} keyword from Issue Tracker template is empty
Status: NEW
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Issuetracking Framework (show other bugs)
Version: 7.3
Hardware: PC Linux
: P4 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
: 222379 (view as bug list)
Depends on:
Blocks:
 
Reported: 2012-09-17 14:33 UTC by Ralph Ruijs
Modified: 2012-11-26 12:14 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Comment 1 Tomas Stupka 2012-09-17 16:45:09 UTC 
> {message} keyword from Issue Tracker template is empty
we stopped adding redundantly the issue reference to the issue comment as that made no sense at all (just look on it from that point). So in your case the text is empty because there actually was no commit msg explicitly added by you. If you generally do not write commit messages, you should change the template so that it doesn't contain the {msg} variable (and label). 

Agree that it might be confusing, but not sure what would be the right thing to do - maybe generating some dummy text e.g. "NO COMMIT MESSAGE" would do the thing. 

also note that generally people are expected to write commit messages.
Comment 2 Ralph Ruijs 2012-09-18 08:35:29 UTC 
(In reply to comment #1)
> > {message} keyword from Issue Tracker template is empty
> we stopped adding redundantly the issue reference to the issue comment as that
> made no sense at all (just look on it from that point). So in your case the
> text is empty because there actually was no commit msg explicitly added by you.
> If you generally do not write commit messages, you should change the template
> so that it doesn't contain the {msg} variable (and label). 
> 
> Agree that it might be confusing, but not sure what would be the right thing to
> do - maybe generating some dummy text e.g. "NO COMMIT MESSAGE" would do the
> thing. 

If the behavior of a feature changes (I can't even remember when I was introduced to this), I think you would want to inform the user better. Only after the change has been pushed and the comment added to the issue, I found out the message is empty. An empty message: label looks a bit stupid, maybe a warning in the dialog if it would be empty?

> also note that generally people are expected to write commit messages.
Comment 3 Petr Somol 2012-09-18 08:45:03 UTC 
> If the behavior of a feature changes (I can't even remember when I was
> introduced to this), I think you would want to inform the user better. Only
> after the change has been pushed and the comment added to the issue, I found
> out the message is empty. An empty message: label looks a bit stupid, maybe a
> warning in the dialog if it would be empty?

I agree. Empty messages should be prevented, especially if it is due to change of feature behavior which is previously unknown to users. A warning in the dialog as suggested above would help.
Comment 4 Tomas Stupka 2012-11-26 12:14:22 UTC 
*** Bug 222379 has been marked as a duplicate of this bug. ***