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 183682 - Option to set Target Milestone upon commit
Summary: Option to set Target Milestone upon commit
Status: RESOLVED FIXED
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Bugzilla (show other bugs)
Version: 6.x
Hardware: All All
: P3 normal (vote)
Assignee: Tomas Stupka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-08 01:43 UTC by Jesse Glick
Modified: 2011-01-07 01:10 UTC (History)
2 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2010-04-08 01:43:22 UTC
100407-2b245ede8704. It is nice that when committing you can also close a bug as FIXED and add a comment with the changeset ID. But I usually also want to set the Target Milestone, say to "6.9". Invariably I forget, the bug is closed as FIXED with TM=TBD, and I need to go back and make its metadata consistent by setting TM.

Would be better if there were an option in the commit dialog to also update the TM at the same time it is closed. The dialog could remember the last-selected TM for convenience.
Comment 1 Tomas Stupka 2010-04-08 05:46:27 UTC
> I need to go back and make its metadata consistent by setting TM
the issue should be opened in an editor tab right after the commit, feel free to file another issue if that doesn't happen in your case

however, i agree that it would be useful to have access also to other issue fields. Could hotfix the milestone with a switch as it seems to be a typical usecase with nb bugzilla.

cc xdesign
Comment 2 Jesse Glick 2010-04-08 12:46:18 UTC
(In reply to comment #1)
> the issue should be opened in an editor tab right after the commit

Yes, this works, which does help. Even if that is enough to remind me to set the TM, the result is two separate changes to the issue, meaning two emails, which is undesirable.

> Could hotfix the milestone with a switch

Something like the following?

  -J-Dnetbeans.bugzilla.target.milestone=6.9

> as it seems to be a typical usecase with nb bugzilla.

And I think in many other instances too. Some project admins do not bother to set up values for this field, but I have experience with e.g. Apache Ant using TM similarly to us.
Comment 3 Tomas Stupka 2010-04-08 13:09:25 UTC
> Something like the following?
> -J-Dnetbeans.bugzilla.target.milestone=6.9
yes.

maybe a bit more generic schema, something like 
-J-Dnetbeans.vcshook.bugzilla.[bugzilla_field_name]=[value]

so in our case it would be 
-J-Dnetbeans.vcshook.bugzilla.target_milestone=6.9
Comment 4 Tomas Stupka 2010-04-12 09:18:51 UTC
http://hg.netbeans.org/cdev/rev/93044cbeb816
fixed
Comment 5 Tomas Stupka 2010-04-12 09:21:09 UTC
switch 
netbeans.vcshook.bugzilla.[fieldname]=[value]

e.g.
netbeans.vcshook.bugzilla.target_milestone=6.9
Comment 6 Jesse Glick 2010-04-12 14:57:53 UTC
Thanks, I will try that for a while so we can see if a GUI option would be useful.
Comment 7 Quality Engineering 2010-04-13 17:35:11 UTC
Integrated into 'main-golden', will be available in build *201004131450* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress)
Changeset: http://hg.netbeans.org/main/rev/93044cbeb816
User: Tomas Stupka <tstupka@netbeans.org>
Log: Issue #183682 - Option to set Target Milestone upon commit
Comment 8 Jesse Glick 2011-01-07 00:54:35 UTC
Seems to have stopped working recently.

I will note that this issue did not have its Target Milestone set. :-)
Comment 9 Jesse Glick 2011-01-07 01:10:55 UTC
Never mind, I guess it is working; cache problems in browser, I guess.