bug-tracking

问题 I need to update same field to same value for hundreds of workitems in TFS. Is there any way to do it in a batch instead of updating them manually one by one? 回答1: You can do this in Excel : Open the work items in Excel, via: right click a query in Team Explorer -> open in Excel multi-select some work items in a WIT result pane, then right click -> open in Excel load Excel, use Team -> Import to load a predefined query open a *.xls file that is already bound to TFS Make your bulk edits Click

问题 I've been looking at setting up Redmine, Trac, or JIRA to track issues. I want to be able to have my development team create internal tickets that are never seen by clients, while clients can create/edit tickets that are seen by the internal team. From the Trac documentation, you can set permissions to create or view tickets, but it doesn't seem to allow for viewing only certain tickets. It may be possible with Trac Fine Grained Permissions, but doesn't appear so. The Redmine documentation

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 4 months ago . Currently we use FogBugz for tracking issues and found it to be ok. I'm looking for something else that can allow end users the ability to track their cases along with us. And something that actually works well with email. I've found a few alternatives that support those

问题 I noted that in BitBucket when your commit log contains a number like #12 this number is linked to the bug number 12. I found this feature interesting, and I wonder if there is any keyword that would allow me to mark the issue as resolved from the commit log instead of going to the web interface each time. If BitBucket doesn't do it, could you point a system that does? 回答1: Bitbucket already supports marking issues on commit using the Issues service. The issues service scans commit messages

问题 I use trac to manage my projects and I'd like to organize wiki pages the same way trac project does, i.e. by category, subcategory, etc. TitleIndex page on trac site gives a good explanation of the result I want to obtain. How do I achieve this? 回答1: First of all, you can create hierarchically wiki pages, just by modifying the url, and press enter. It is also possible to create a wikilink first, and then press the red link. For example, when your trac home page is http://trac.server.local

问题 I know about Fossil but are there any alternatives? Something small and easy to install/configure. 回答1: I know there are quite a few git-based wikis such as git-wiki, WiGit and gitit. A simple google search will bring up many others, I'm sure. I also know of some git-based bug trackers such as ticgit which basically lets you keep your tickets in a separate branch of a git repository. There's also DisTract. But I'm not aware of anything else aside from Fossil that really tries to do what it

问题 I have this slider: And it works like a charm in almost all browsers (Firefox, Opera, Safari, and even the designer-killer browser, IE). But in Chrome 11 (I have to support this version of Chrome) and lower versions the right button falls down. I was tracking to see why it behaves so, and I came across something really interesting, but at the same time annoying. For my left and right buttons, I have a very simple CSS rules: #rightBtn { background: url(/images/rightBtn.png) 0 0 no-repeat;

问题 Closed . This question is opinion-based. It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post. Closed 4 years ago . I am involved in this project, Pinta, and we are currently using GitHub for our development. We all love Git and GitHub and want to keep using it. However, now the project is getting stable and involved, and it's time we started using a more capable bug tracking system than

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 6 years ago . Besides the painful-to-install non-Windows Bugzilla, what open-source issue tracking programs can be recommended that are just as good

问题 In my current company there isn't clear understanding between the test and development teams as to how severe a bug should be? There are arguments which go back and forth to reduce or to increase the severity. We are not as of now aware of any documents which lays the rules. The tester raises the bug and assigns priority based on his intuition. The developer would request a change based on his load or some other factor. How are severity/priority of bugs classified? Are there any standards