Anonymous | Login | Signup for a new account | 2012-09-13 19:33 PDT |
Main | Blog | My View | View Issues | Change Log | Roadmap | IRC Chat | Repositories | Scrum Board |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||||
176 | Source Integration | WebSVN | public | 2010-09-29 09:37 | 2010-09-29 09:37 | ||||||
Reporter | Harvey Chapman | ||||||||||
Assigned To | |||||||||||
Priority | normal | Severity | feature | Reproducibility | always | ||||||
Status | new | Resolution | open | ||||||||
Product Version | 0.13 | ||||||||||
Target Version | Fixed in Version | ||||||||||
Summary | 176: Add ability to re-import single changsets | ||||||||||
Description | It usually takes new hires a few commits before they remember to put the mantis issue references into their commit messages. We end up going back into svn and editing the messages manually. The only way to get mantis to see those changes is to Import Everything which has the side effect of sending out e-mails for every bug ever fixed and linked to svn. Suggested feature: - Add a re-import option next to Edit for changesets. Question: - As best as I can tell, Editing a changeset only updates information in mantis. Is this true? | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
![]() |
|||
Date Modified | Username | Field | Change |
2010-09-29 09:37 | Harvey Chapman | New Issue |
Copyright © 2000 - 2012 MantisBT Group
Time: 0.1226 seconds. memory usage: 8,316 KB |