Search Results

Search found 23890 results on 956 pages for 'issue'.

Page 1/956 | 1 2 3 4 5 6 7 8 9 10 11 12  | Next Page >

• What Issue Tracking System to select?

  - by Mikee

  What Issue Tracking Sytem is the most appropriate for fast, big, multilingual and international websites? The system has to handle both technical and content/editorial issues. What's the size and type of your site do you run? Whart System are you using for the keeping it state of the art? Thanks a lot for sharing your good or bad experience.

  Read the article

• Requirements of an issue/bug tracker

  - by James Brooks

  I've been looking at various issue/bug trackers available on the net. There are some very good ones, but I'm unable to use them as my server does not support Perl/Ruby (for example), I'm not too bothered however because I am able to write code in PHP and as such would prefer something in that language. So I've taken it upon myself to write a custom issue tracker system. As of now it's in early planning stages, and before I continue, I'd like to find out what people need from such an application. My current list of things to add include: Creating/Editing/Deleting issues - both on user and admin level Related issues (similar to that of STO) Admins will be able to create builds/milestones and version control of projects Admins will be able to assign users/groups to a project Roadmap of projects Possible SVN integration with Git? What do you think? There are a couple more things I'd like to add, but I'm sure you'll think of a better way of adding such feature. What would you like to see from an issue tracker?

  Read the article

• What Issue Tracking System to select?

  - by Mikee

  What Issue Tracking Sytem is the most appropriate for fast, big, multilingual and international websites? The system has to handle both technical and content/editorial issues. What's the size and type of your site do you run? Whart System are you using for the keeping it state of the art? Thanks a lot for sharing your good or bad experience.

  Read the article

• What to do when issue-tracker is down?

  - by Pablo

  It has happened in our team that our issue-tracker is down. Happens about once a week now (yes, wow), and there's not really much we can do to get it back up, since it's hosted by our client in a different timezone. It sometimes takes several hours for it to be operative again. In the meanwhile, we can't really tell which issues we were working on, and in case we do, we cannot update those issues, as in moving them through the workflow, logging used hours, checking the issue's description, leaving comments, and so on. So the question is: how can we, as a team, work in the meanwhile so that when the issue-tracker is up again, we have the least possible hassle updating it with what we've been working?

  Read the article

• Where can I find accessible bug/issue databases with complete revision history

  - by namenlos

  I'm performing some research and analysis on bug/issue tracking databases and more specifically on how programmers and teams of programmers actually interact with them. What I'm looking for involves understanding how those databases change over time. So what I don't need for example: is a database of all the bugs of some open source project as the bugs exist today. What I do need is a complete set of revision history for every issue/bug in the database. This would enable me to pick a specific datetime and say here were the list of all the issues/bugs that existed at that moment in time. Anyway know of some publicly accessible issue/bug databases that expose this revision data? Ideally, the revision would look something like this (shown for a single bug, with two revisions) ISSUEID PRI SEV ASSIGNEDTO MODIFIEDON VALIDUNTIL 1 2 2 mel apr-1-2010:5pm apr-1-2010:6pm 1 2 3 steve apr-1-2010:6pm NULL

  Read the article

• Requirements/issue tracker similar to online spreadsheet

  - by Maxim Eliseev

  Is there a requirements/issue tracker software which is similar to Google spreadsheet? We have Fogbugz but I find it more heavyweight and slow than a simple spreadsheet. Is there a Fogbugz alternative which is - fast - can show issues/requirements as a spreadsheet (at) and allows in-place editing - supports tree structures (where issue can have child issues)? It is required for a small project. There will be 2 developers and 1-2 other users. I guess that only one user will be actively maintaining it. UPDATE I do not say that a spreadsheet is better than Fogbugz or similar tools. In fact I am looking for a tool which is similar to Fogbugz and could replace a spreadsheet, but faster than Fogbugz and has an additional feature (table-like mode). I'd like to find a tool which can operate in a mode which looks like a table (one row per issue) but has a rich set features (similar to Fogbugs and JIRA). I find Fogbugz (and similar tools) inconvenient because I must enter the web form in order to edit anything. In-place editing (when issues are shown as a table) would be much faster.

  Read the article

• Solution with multiple projects and (GitHub) single issue tracker and repository

  - by Luiz Damim

  I have a Visual Studio solution with multiple projects: Acme.Core Acme.Core.Tests Acme.UI.MvcSite1 Acme.UI.MvcSite2 Acme.UI.WinformsApp1 Acme.UI.WinformsApp2 ... The entire solution is checked-in in a single GitHub (private) repo. Acme.Core contains our business logic and all UI projects are deployables. UI projects have different requirements and features, but some of them are implemented in more than one project. All issues are opened in a single issue tracker and classified using labels ([MvcSite1], [WinformsApp1], etc) but I'm thinking it's starting to get messy. Is it ok to use a single repository and issue tracker to track multiple projects in one solution?

  Read the article

• Simple issue tracker for 1-2 developers

  - by devoured elysium

  (I'm not sure whether this pertains to the realm of programmers@se or so@se) I'm currently working mostly alone on a project (in Java). I'm mostly alone as I have an advisor that gives me high level instructions on what to do, and will seldom make any code contribution. She will code in a couple of acceptance tests from time to time, though. I've never used an Issue Tracker before, and was thinking about starting to use one now, as I'd like to have a place where I can log possible bugs I find and keep track of them in a centralized manner. Would it be possible to integrate the issue tracker with Eclipse, better yet. So here are the constraints: It's NOT a open-source project. Our code is not to be shared with anyone! we are and will be using Subversion; we have our own Subversion server and we will keep using this same Subversion server; it must be free; it must allow at least 2 users. What is your advice on what to pick? I'm looking for the simplest solution available!

  Read the article

• Can an issue tracking system be distributed?

  - by Klaim

  I was thinking about issue tracking software like Redmine, Trac or even the one that is in Fossil and something hit me: Is there a reason why Redmine and Trac are not possible to be distributed? Or maybe it's possible and I just don't know how it's possible? If it's not possible, why? By distributed I mean like Facebook or Google or other applications that effectively runs on multiple hardware a the same time but share data.

  Read the article

• ubuntu 12.10 - nvidia gtx 550 ti proprietary drivers issue

  - by Phill

  I have installed Ubuntu 12.1 and own the nvidia gtx 550 ti (no integrated video). Installed it just fine but the buttons and text seem to get scrambled if using the nouveau drivers I guess. I tried installing the proprietary drivers manualy and from the Additional Drivers tab in software sources but every time I do that after it restarts the menus and icons dissapear an the only way getting them back is to revert to the nouveau drivers. I've tried noumerous attempts ending up reinstalling it. Any help would be apreciated, thanks.

  Read the article

• How to manage an issue tracker's backlog

  - by Josh Kelley

  We've been dutifully using Trac for several years now, and our "active tickets" list has grown to almost 200 items. These include bugs that are too low priority and too complicated to fix for now, feature requests that have been deferred, issues that have never really generated complaints but everyone agrees ought to be fixed someday, planned code refactorings and other design infelicities that we don't want to lose track of, etc. As a result, with almost 200 of these issues, the list is almost overwhelming; it's no longer useful as a source of what needs to be worked on right now. What's the best way to keep track of issues of this sort? Part of the problem is that some of these issues are such a low priority that they may never get done. I hate to lose track of these items (similar to not wanting to throw something out of my house in case I might need it someday); do I need to throw them out regardless (by marking them as wontfix) and assume I can find them in the future if I ever do need them?

  Read the article

• Why do some open source projects do not allow to report issues in a public issue tracker?

  - by linquize

  Why do some open source projects do not allow to report issues in a public issue tracker? Those projects requires the issues to be reported via email, and the issues may be forwarded to people in mailing list. Users may repeatedly report the same issue if there is no public issue tracker, as they have no easy way to know what have been reported before. The project team members need to spend extra time answering those repeated issues. Some projects do have a public issue tracker, but the issues are still reported through email and they are posted only by the project team only after filtering. It does not allow anyone to report directly in issue tracker. (example: SVN) Such arrangement is not transparent nor open, which I think it violates the philosophy of open source. And it is outdated.

  Read the article

• Why do some open-source projects NOT have a public issue tracker?

  - by linquize

  Why do some open source projects not allow to report issues in a public issue tracker? Those projects require the issues to be reported via email, and the issues may be forwarded to people in a mailing list. Users may repeatedly report the same issue if there is no public issue tracker, as they have no easy way to know what has been reported before. The project team members need to spend extra time answering those repeated issues. Some projects do have a public issue tracker but the issues are still reported through email and they are posted by the project team only after filtering. It does not allow anyone to report directly in issue tracker (example: SVN). Such arrangement is not transparent nor open, which I think violates the philosophy of open source. And it is outdated.

  Read the article

• What is the role of traditional issue tracker when Scrum / Kanban board is used?

  - by Borek

  From a very high level view, to me it seems there are generally 2 types of Project Management tools: Traditional issue trackers like Fogbugz, JIRA, BugZilla, Trac, Redmine etc. Virtual card boards / agile project management tools like Pivotal Tracker, GreenHopper, AgileZen, Trello etc. Sure, they overlap in one way or another, e.g. Pivotal Tracker tasks can be imported to JIRA, GreenHopper itself is implemented on top of JIRA issue base etc. but I think one can still see the difference in orientation between those two types of tools. Traditional issue tracker seems to be used even in companies otherwise doing agile project management. My question is, why do they do that? I also feel that we should use an issue tracker in my company but when I'm thinking about it, I'm not actually sure why should we need it. For example, Trello development seems to be managed by using Trello itself (see this virtual wall) even though they have access to Fogbugz, one of the best issue trackers around. So maybe we don't need traditional issue tracker when we'll be doing 100% of our work in an agile manner using one of the agile PM tools?

  Read the article

• Wiki & issue-tracking in one system?

  - by torbengb

  I'm looking for an integrated solution that combines documentation of a software system with tracking of bugs, change requests and feature requests. Requirements: Documentation using a wiki would be nice, preferably one supporting CamelCase or other automatic linking. Issue tracking must allow a customizable workflow and optional e-mail notifications. Known alternatives: FogBugz is an awesome issue tracker, but the wiki appears to be somewhat awkward. Trac's wiki is average (though not as nice as Foswiki.org) but I don't know how good the integrated issue tracker is. What would you recommend? What systems offer the best combination of documentation and issue tracking?

  Read the article

• Issue tracker for web agency workflow

  - by Eirik Johansen

  We're looking into implementing an issue tracker for our web agency. The problem is that most issue trackers seem to revolve around the assumption that an issue is a bug, whereas in a web agency environment, a lot of the issues (request, or whatever you want to call them) are about changes and additions to a current web site. It also seems to me that a lot of issue trackers assume that you're working on one main software project, and uses that project as the focus of the tracker. A good issue tracker for a web agency would be one which puts each separate client and their issues at the heart of the system, making it easy for them to track and report issues. Does anyone know of a good issue tracker for the web agency workflow? What are other people using?

  Read the article

• Help Desk Issue Tracking/Ticketing System for MOSS 2007

  - by ITGuy24

  We are looking for a MOSS 2007 webpart for help desk issue tracking and ticketing. Any recommendations? It doesn't have to be too fancy, but would like something a little more comprehensive then the helpdesk template built into MOSS.

  Read the article

• Can Office Project Server 2010 handle issue tracking?

  - by JL

  I have a scenario where I want to be able to allow customers to login to a customer facing portal on the web, and log issues / bugs. Internal team members should then be notified via email and the issue should be logged in Project Server. The ticket status should be Open, until either resolved or close, where the customer will be notified via email. Is this possible to do using Microsoft Project Server 2010? The question could also be can customers submit bugs to office 2010 projects via a custom web form of some kind, and can project handle the back-end gracefully.

  Read the article

• What level/format of access should be given to a client to the issue tracking system?

  - by dukeofgaming

  So, I used to think that it would be a good idea to give the customer access to the issue tracking system, but now I've seen that it creates less than ideal situations, like: Customer judging progress solely on ticket count Developers denied to add issues to avoid customer thinking that there is less progress Customer appointing people on their side to add issues who don't always do a good job (lots of duplicate issues, insufficient information to reproduce, and other things that distract people from doing their real job) However, I think customers should have access to some indicators or proof that there is progress being done, as well as a right to report bugs. So, what would be the ideal solution to this situation?, specially, getting out of or improving the first situation described?

  Read the article

• Package upgrade on Ubuntu raid server and grub setup issue

  - by RecNes

  I have remote Ubuntu 10.10 server running on raid system. I did package upgrade yesterday night for security reasons. During the upgrade, grub installation screen appeared and asked me which partition I wanted to install grub. Options are sda,sdb,md1 and md2. I decide to install them on both sda and sdb partitions. I wondering, was I make true decision? If machine get reboot is it can be boot up safely? You can find fdisk output and fstab mount points below: Fstab: proc /proc proc defaults 0 0 none /dev/pts devpts gid=5,mode=620 0 0 /dev/md0 none swap sw 0 0 /dev/md1 /boot ext3 defaults 0 0 /dev/md2 / ext3 defaults 0 0 Fdisk: Disk /dev/sda: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00029bb5 Device Boot Start End Blocks Id System /dev/sda1 1 262 2102562 fd Linux raid autodetect /dev/sda2 263 295 265072+ fd Linux raid autodetect /dev/sda3 296 91201 730202445 fd Linux raid autodetect Disk /dev/md0: 2152 MB, 2152923136 bytes 2 heads, 4 sectors/track, 525616 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 271 MB, 271319040 bytes 2 heads, 4 sectors/track, 66240 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md2: 747.7 GB, 747727224832 bytes 2 heads, 4 sectors/track, 182550592 cylinders Units = cylinders of 8 * 512 = 4096 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Disk /dev/md2 doesn't contain a valid partition table Disk /dev/sdb: 750.2 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00088969 Device Boot Start End Blocks Id System /dev/sdb1 1 262 2102562 fd Linux raid autodetect /dev/sdb2 263 295 265072+ fd Linux raid autodetect /dev/sdb3 296 91201 730202445 fd Linux raid autodetect

  Read the article

• Looking for issue tracker software for residential property management

  - by Rob

  This question is about a computer software (as per SU guidelines) application for centrally tracking issues concerning the management of a residental block of flats (apartments as they say in the US and France). Issues are incidents - and their resultant unplanned maintenance to address them, also planned one-off maintenance and also regular planned routine maintenance. I live in a block of flats (apartments), and along with other residents, are looking to more closely watch over issues with the communal, shared areas of the premises (corridors, courtyards, stairs, lifts, lights, trash/bin shed, bike stands, parking areas etc) and their maintenance, currently done by a property management company. Our own homes are our own affair internally, its the outside communal areas that I have the interest. The aim being to control costs and possibly reduce them, by proactively managing the property using historical data to predict issues and also to scrutinise maintenance charges against such data to ensure that the costs are as expected. Trending could also be established whereby recurrences of things can be detected and pre-empted to reduce costs. As a software professional, I'm aware of Bugzilla, eventum being free tools for software - which could be customised to fit this application, but wondered if there was something more appropriate. It might be useful for such software to be on a web server, with secure access, so that residents can log in and view the issues.

  Read the article

• Vote based issue tracking and feature request system? [closed]

  - by meds

  I'd like a system where people can sign up and post bugs or feature requests they might have and have access to seeing other bugs and feature requests they can vote on based on which they want the most. Something like http://feedback.unity3d.com would be great. edit: I'm not exactly sure how this isn't 'a real question', perhaps people are incapable of inferring a question because of a lack of a question mark so here's one: '?' is that better? (that makes two).

  Read the article

• Most user-friendly issue tracker?

  - by Kugel

  Sorry if this has been asked before, couldn't find anything specific. I'm looking for the most user-friendly issue tracker. Currently I'm using Trac. I'm looking for these 2 features: Very easy to create new ticket Email to ticket conversion (with attachements). The customers should be glad to use it (not avoid it like Trac). More often than not I get e-mails as bug reports and putting them into Trac wastes my time. I would really love to just hit forward and the ticket would appear in the issue tracker.

  Read the article

• Building an Issue Tracker Plugin for TortoiseSVN

  - by Oded

  I've read a lot about IBugTraqProvider interface and implementing an issue tracker into the commit dialog of TortoiseSVN. IBugTraqProvider is written here. Is there a more simpler way not to do it, building the plug-in and installing it on TortoiseSVN. The Document is not that clear that a developer can create its own plugin. I'm working with SalesForce as the Issue Tracker, and retrieved the WSDL file to integrate with the Working Items. Now I need to know how to connect it to TortoiseSVN. Please any suggestions?

  Read the article

• Building an Issue Trecker Plugin for TortoiseSVN

  - by Oded

  I've read a lot about IBugTraqProvider interface and implementing an issue tracker into the commit dialog of TortoiseSVN. IBugTraqProvider is written here. Is there a more simpler way not to do it, building the plug-in and installing it on TortoiseSVN. The Document is not that clear that a developer can create its own plugin. I'm working with SalesForce as the Issue Tracker, and retrieved the WSDL file to integrate with the Working Items. Now I need to know how to connect it to ToortoiseSVN. Please any suggestions?

  Read the article

1 2 3 4 5 6 7 8 9 10 11 12  | Next Page >