Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 


Forgot your password?
Close
typodupeerror
×
Communications Software

Ask Slashdot: Issue Tracker For Non-Engineers? 144

Posted by timothy from the who-did-what-when-where-why-and-to-whom? dept.
purplie writes My non-technical spouse is an analyst in a small county government department, a handful of people plus some contractors for projects. Their project/task management is mouth-to-mouth, sticky notes, and emails, and it's driving them crazy. I want to suggest something like an issue tracker. It would have to work for tasks both large (year-long investigations) and small (arranging catering for a meeting). The issue trackers I'm familiar with are too software-development-oriented, or make too many assumptions about your 'agile' religion. Are there any good options for non-engineers? They use mainly Windows and have iPads. I don't like web-based tools, but that might work better for them because they don't have administrative privs on their machines. Something that also incorporates a wiki might be nice. There will be resistance if it's not really easy to use.
This discussion has been archived. No new comments can be posted.

Ask Slashdot: Issue Tracker For Non-Engineers? More

Ask Slashdot: Issue Tracker For Non-Engineers?

Comments Filter:

  • Redmine is good (Score:5, Insightful)

    by Anonymous Coward on Thursday March 12, 2015 @12:36PM (#49242363)

    Redmine is pretty flexible and has worked for us across multiple disciplines.

    • +1 for redmine (Score:5, Funny)

      by j1976 ( 618621 ) on Thursday March 12, 2015 @12:57PM (#49242613)

      I've successfully managed to trick a bunch of psychologists into using redmine for issues management. These guys are the epitome of non-techies.

      • + another one for Redmine. Works pretty well, easy to customize, relatively clear, and sends a bunch of email to ensure that relevant parties see updates.

    • Re: (Score:2, Informative)

      by garyisabusyguy ( 732330 )

      I'll probably get down-modded for this, but Sharepoint is a pretty capable tool for issue tracking

      I was working at a non-profit that used MS Office as their primary authoring tool
      We were able to license Sharepoint for a pittance and decided to support it on an enterprise level
      My group used Sharepoint lists to track all work in progress, publish white papers and best practices, and produce new website for the organization (via Sharepoint365)

      I would suggest that they speak with their software rep for MS apps

      • Re: (Score:2, Informative)

        by Anonymous Coward

        If you get down modded it will be because your post is unrelated to the GP you replied to, likely just to end up higher on the page.

        • Thanks for the pointers, but the 'parent' that I replied to was identifying a project tracking software and there seemed to be discussion about getting non-technical people to us such software. I felt that it was an appropriate place to discuss experiences with 'other' software

          and it was close to the top of the page :)

      • No downmodding from me.

        Sharepoint seems to be universally hated by the techies I work with. Maybe it's well matched to non techies.

        • My initial reaction to it in 2005 was Gah! what is this FrontPage?
          The most recent work we did in it relied heavily on Angular and a palette of templates that made for wordpress-like presentation
          We had very spotty adoption by nontechnical people, i.e. a smattering of people who would take the time to learn how to configure their group pages, but most people coming back to us for anything like adding/configuring a list or other web part
          Eventually we handled it like mini-dev projects with 2-3 one week sprints

    • Agreed.

      While Redmine definitely has plenty of plugins and features for "agilism," it's easy to bypass or ignore them. It also allows SSO for Windows users with fallback to user+password, sends change and assignment notices by email, and has a Wiki built in. You can auto-create recurring issues if that's needed (think assigned weekly/monthly tasks), and there's a knowledge-base plugin that we've also found useful. It is project centered, where you can assign subsets of users to projects when they're cr

    • Re: (Score:2)

      by frisket ( 149522 )
      Is it mobile-aware/responsive? demo.redmine.org looks pretty grim
    • Another +1 for Redmine. Very simple to use and manage without pushing any manifestos down your throat.

  • Asana (Score:2, Informative)

    by Anonymous Coward

    https://asana.com/ [asana.com] is the most pleasant issue tracking software I've used.

    • I've used Asana as well, and while it's not perfect, it definitely has value. You can assign things to folks, segment by project, and set due dates. You'll still want a proper calendar application for meetings, though.

  • Trello (Score:5, Interesting)

    by ry4an ( 1568 ) <ry4an-slashdot@NospaM.ry4an.org> on Thursday March 12, 2015 @12:41PM (#49242419) Homepage

    Consider Trello. It's not strictly an issue tracker, but it's very good for this sort of thing and already popular outside of software circles.

    • I second this. Trello is professional and simple.

      • Re: (Score:1, Interesting)

        by cyborg_monkey ( 150790 )

        it looks like a mess.

        • I agree. Its how-to section welcoming beginners doesn't describe how-to do anything. Features are demonstrated and users are left clicking around trying to figure out how to reach those features. During the process of figuring that out, users end up creating boards that can't be deleted but won't be wanted, and we find that cards can not be deleted -- only archived. And they can't be recovered from archive, so who exactly is archiving them and for what?

          Trello does look like a mess, but it looks like

          • You do know that you're not allowed to have negative opinions anymore, right?

            Of course, but you're expected to write a post explaining your contrary position, ideally backed up with a cite or your personal (anecdotal) experience with the product in question, not just mindlessly downvoting something based on the fact you played with Trello for four minutes, or that you disagree based on ideology.

            OP: We use Trello for the tasks you're asking about, and it works well. I'd say the only hiccup is it's a

            • That's sensible, but remember that no one person can both comment and downvote on Slashdot. If you moderate, then the moment you comment on that page, all of your moderation is reversed.

              Trello is *just* on the cusp of awesome though! I've signed up and will be watching that site's development closely.

    • Another +1 for Trello, due to lack of mod points. It works well on mobile and ipad and even has an app (I think). And the metaphor is dead simple to use.

    • For quite some time my team used trello as our software issue tracker before we got Jira set up. It works quite well.

      • So sorry to hear you ditched something useful, simple and well-designed for Atlassian's overpriced bloatware. What was the appeal, how particular buggy versions of Java are required for some of their shi or how batch job threads like mail queuing stall out for no reason? Maybe put in a cron job to restart the festering pile of shit every morning and hope to god it holds together until quitting time.

        • Well I did not install it and nor do I maintain, but it is way better (to use) than bugzilla from my experience.

          If it were up to me we would be using GitLab issue tracker (which we also use to store our code). but my company is one of those obsessed with time-keeping every single thing we do so they can charge the client by the hour and Jira has some plugins that do all the processing for them.

          Honestly it has a bunch of stuff I don't use that just gets in the way, but I got used to it after one week and the

    • I personally like Trello which is what is being used in Stack Exchange (makers of Stack Overflow and its ilk) http://blog.stackoverflow.com/... [stackoverflow.com]

      We are an online company: we’ve been remote from day one and still to this day over half of the team (aside from sales) works from home. The only way to make that work is to keep the nexus of activity online: in chat rooms, Google Hangouts, Trello boards, etc. This keeps everyone on equal footing, whether you’re in the office or working from home.

      The article was the one that introduced me to the tool and I am impressed by it. Though it still needs some explanation of how to use it. I suggest you look at Kanban but don't mention it as a methodology etc... just explain how to group the work and be done with it.

    • Re: (Score:2)

      by jtara ( 133429 )
      It's funny, I tried Trello first for a project that went nowhere - the wanna-be backer was too busy on ski-trips, and his "people" were too busy partying while he was gone... so I put it to rest. Then I started on a project where I need to coordinate with another developer who uses Trello. There are some oddities that take getting used to, but I am really loving it. In the mean time... the wanna-be backer from the first project manages his real-estate (some apartments and commercial buildings). He started

    • Re: (Score:2)

      by Jawnn ( 445279 )
      Consider the requirements, no..., actually read and consider them, and then try to tell me that Trello is a good fit. Nothing wrong with Trello, mind you. It's a great tool, but not for simple issue tracking of the sort the OP's talking about.

    • Re: (Score:2)

      by jerpyro ( 926071 )

      I looked at Trello but then settled in on ProjectPlace instead. Mostly because the category views were easier to manage.
      http://todo.projectplace.com/ [projectplace.com]

      Both are good tools for managing task states though.

  • Trello (Score:4, Informative)

    by colenski ( 552404 ) on Thursday March 12, 2015 @12:43PM (#49242451) Homepage
    I have used Trello [trello.com] for the coordination of issues for a large-ish project with coders, project managers, and general business people, it works well, very drag-and-drop-y, nice card metaphor.

  • set up spreadsheets for each issue and use the cells to track progress

    • set up spreadsheets for each issue and use the cells to track progress

      I endorse this idea, especially since OP expects to get a good software solution from a bunch of people he just insulted by implying they're religious nuts.

    • set up spreadsheets for each issue and use the cells to track progress

      I might be picky, but I find a spreadsheet that takes 1 or 2 seconds to refresh each time you enter a new number in a cell to be a bit irritating.

      If you want a spreadsheet solution just use Excel (or LibreOffice) to avoid your users dying of boredom.

  • Your solution has to work on Windows and iPads, but you'd rather not use a web-based product? I guess it's possible an app that does what you want with robust Windows and iOS clients exists, but I wouldn't count on the "robust" part if I were a betting man. That's coming from someone who runs Outlook an a Mac, so I'm admittedly jaded when it comes to claims of cross-platform compatibility.

    I've used Redmine in the past. Web-based, open source, pretty easy to use. Some of my colleagues hate it, so YMMV

    • Redmine is great. I use it for all our internal IT projects and also service desk. On desktop computer there is not really a need for native client as web based version works OK. For tablet and phones there are few native clients that use Redmine API and once I checkd them RedminePM worked very well for us.

  • Task scheduling is not issue tracking (Score:5, Informative)

    by cloud.pt ( 3412475 ) on Thursday March 12, 2015 @12:48PM (#49242513)

    You don't want issue tracking - you want task scheduling and task completion methodologies. The non-engineer have schedules to fulfill which are usually not associated with a deliverable but a task. If there's no deliverable, there's no bug, no feature, i.e. no ISSUE. So tracking issues loses the focus. Issues aren't always tasks in trackers and that's why those are so tied to code, since they mold issues to whatever a release date/agile software development needs.

    Unlike issues, tasks always translate to effective actions to undertake someplace, sometime, with someone, for whatever reason.

    Post-its are still used nowadays because they do their job representing tasks, and their physical form, order or the fact it is in the trash can imply its relevance, priority, date/time-frame and status. Tell her to keep using tools she's comfortable with, but customize a variation of KANBAN for her team's specific needs. And then maybe decide if a web platform or a physical board make more sense in her context, and the learning curve is acceptable. Post-its + a board or Trello are a good place to start.

    • You don't want issue tracking - you want task scheduling and task completion methodologies. The non-engineer have schedules to fulfill which are usually not associated with a deliverable but a task. If there's no deliverable, there's no bug, no feature, i.e. no ISSUE. So tracking issues loses the focus. Issues aren't always tasks in trackers and that's why those are so tied to code, since they mold issues to whatever a release date/agile software development needs.

      This ^10 - the OP is trying to force a squa

      • Re: (Score:1)

        by mrzaph0d ( 25646 )

        yeah, gotta agree. without the methodology, no one will use it. plus, if the users don't even have admin on their machine, good luck installing stuff and keeping it installed when the real IT department finds out.

        go for the offline solution like a whiteboard. put it in a location where everyone has to pass at least once a day, or in a meeting room where everyone goes to update it together on a regular basis.

        either way, make a point to use it and stick with it, but be flexible enough to make changes to the m

    • Todo lists, like Todoist might also work.

      Hundreds of todo apps turned up with the smartphone wave, but I believe that's the one that best integrates across platforms (Web, Mobile, and even some specific OS apps and MS/Open Source Office suites. Oh and the cloud, I think there's a Gmail plugin too). The main benefit of Todoist though is, like Trello, that they are very easy to get into, but can evolve if you need the added complexity.

      See it like this: you can simplify a code-centric issue tracker like JIRA

  • Jira and Confluence (Score:1)

    by Anonymous Coward

    We use these at work and they tie in together nicely. Jira= issue tracker, Confluence= wiki

    I'm not crazy about them but they get the job done.

  • Request Tracker (Score:1)

    by Anonymous Coward

    RT is very flexible, though there's a bit of admin overhead to get everything set the way you want it. Email integration works well, and on the user side, it is quite easy to use.

    https://www.bestpractical.com/rt/

    • Seconded. If the larger scope is for project management and all it entails then redmine et al work fine.
      But if one wants a 'trouble-ticket' system that integrates well with email and pagers etc... RT works very well. It does take some time to get it right, but worth in IMO.

  • OpenAtrium (Score:4, Informative)

    by SpzToid ( 869795 ) on Thursday March 12, 2015 @12:53PM (#49242559)

    OpenAtrium is an open-source intranet-in-a-box, its v2.0 version making use of Responsive Design to support all devices, and includes calendaring, an excellent issue tracker, RSS reader/publisher, and can be customized for all kinds of unique purposes (or not).

    www.openatrium.com

    It is the issue tracker used by the current White House for its issue tracking and collaboration purposes.

    http://www.kavehmoravej.com/bl... [kavehmoravej.com]

    https://developmentseed.org/bl... [developmentseed.org]

  • We use Jira at work, it has a nice amount of different plugins for boards. So it's not just a tracker for software. Great when used properly, but needs some training from an educated person who's done it before.

    • Jira doesn't seem super-suited to non-software tasks at the moment, though it can be wrangled into it (it'll still display a lot of software dev-specific info). They are, however, planning to create views for it sometime this year (I think - can't find the reference) which could be used to e.g. coordinate a management team or similar. So probably not super useful right now, but maybe in six months take another look and it might just beat the competition.

  • Maybe something like Tracks [getontracks.org]

    or any of the other pre-packaged issue trackers from turnkeylinux.org [turnkeylinux.org]

  • My few cents... (Score:4, Informative)

    by Sarten-X ( 1102295 ) on Thursday March 12, 2015 @01:03PM (#49242679) Homepage

    There are already a lot of suggestions for which particular package to use, so I'll contribute my thoughts.

    I've used RT [bestpractical.com]. It worked.

    The main feature that helped me move my (financial services) office from word-of-mouth to proper tracking is that RT supported submitting issues by email. We already used internal email extensively for other workflows, so it was easy for me to convince people to send an email to <project>@tracking.<domain>, and they'd get an emailed response showing the ticket number and a link where they could follow the progress.

    RT let me run different projects (which in my case usually meant only 1-3 people) separately, and each project had nice charts showing how many open issues they had to work on. Managers loved that, because they could see who was overloaded and by how much. Each user was also able to create their own dashboard to display when they logged in, so they could get a to-do list first thing in the morning.

    For each project, I could modify what information was needed when a ticket was created. Almost the entire ticket form was customizable, so that was adapted to the project needs. For our financial advisors, they had simple forms with a customer name and a description field. Traders had buy and sell forms with security symbols, amounts, account numbers, et cetera.

    I haven't been in a position to manage very many trackers, so maybe these features are standard-issue. Maybe something else will work for you, but like it said, RT worked for my needs.

    • I agree.

      Our organization relies heavily on RT.

      At first, I hated it. It's ugly, and written in Perl but have grown to really respect it's capabilities.
      It's easy enough for the managers to poke around in and do basic administration, but flexible enough for the engineers to code custom plugins and scripts to extend functionality.

      There is a large community and tons of documentation.

      • +1 for rt

        We have used it for years. And it is mostly awesome. My only complaint is that attachments, comments, and responses all live in the same column in a single table in the database. Making full text searches a tough nut to crack, especially as the system grows. We have stood up a replicant database with a solr search in front of it. To do full text searches of comments and replies without taking down the rt system (ours currently sits at about 12 gb of data)
  • A simple Drupal installation with the addition of the Project Management module would probably solve all their needs. It could setup in about an hour, and it's free.

    https://www.drupal.org
    https://www.drupal.org/project/pm

  • Used Trello, Switched to Asana (Score:1)

    by Anonymous Coward

    Trello is a nice tool and I used it with a group for a while. For my new projects I use asana. It has mobile apps and a very easy to use web interface. It is essentially lists (goals, evaluations, etc) with discussion attached. I find it easier to work with than trello when you have more than just a few projects for the group. I haven't tried trello in a year or so, maybe the higher level organization is better now. Asana is free for small teams (15?).

  • My company uses Jira to track issue, both technical and nontechnical. It is very flexible and customizable.

  • It's not really an issue tracker, but I use it for tracking issues and features during build cycles.

    It's *super* easy to set up and add items.

  • There's an interesting analogy in Stack Exchange, the offshoot of Stack Overflow. While many Stack Exchange sites exist for a wide ranging array of topics (physics, electrical engineering, statistics, parenting, etc.), I've found that the others basically don't work. The questions often don't get answered since the community is way smaller than Stack Overflow, and they are often answered in unhelpful ways with opinions rather than expert suggestions. I think non-engineering tickets would linger for too l

  • Depending on exactly what the needs are, I'd recommend looking at both project management software and software aimed at helpdesk sorts of things. Google for those, and you'll find an endless list. On the project management side, you'll find things like Trello, Asana, and Basecamp. For helpdesk-related things, you might look at things like Desk.com, Zendesk, or Autotask.

    On both of those fronts, there are tons and tons of competing services. There's not really a "best" solution as much as "the one that

  • It varies from organization to organization. As such, solutions need to align with both the workflow and tasks. You've described the tasks, but not the structures of the workflow. It sounds as if both are very broad and ad-hoc.

    I'd start by forming an inventory of tasks and who does them, followed by modeling the data inputs and outputs that drive the (currently undefined and unspecified) processes in the organization and then move on to the processes. After you have a handle about the range of these items,

  • My first semester under my university's co-op program I was a human issue tracker. People would contact me with issues and I would track them in an excel spreadsheet. I would then follow up with various stake holders to track the progress on each item.

    Thinking back on it, it was strange. I spent my college internship acting as a manager...

    Depending on the volume of issues, this doesn't have to be a full time job. One person just needs to be the point of contact, document, and follow up on the items.
  • I use MavenLink [mavenlink.com] to track projects for non programmers (artists on m games, mostly). It's pretty straightforward--you pay a monthly fee per user.

    • Re: (Score:2)

      by Jake73 ( 306340 )

      MavenLink is rather nice. For long-running projects, I think something with Gantt charting is an absolute necessity and most programmer "issue trackers" don't have Gantts. But this is mostly due to their mapping to methodology. Gantts come from waterfall methodologies and that doesn't settle with an agile process.

      Software works well for agile processes but there are a lot of tasks and projects out there that are much more tuned to waterfall methods. Long-running projects, for example, can have tons of depen

  • It is never about the tool (Score:3)

    by MerlynEmrys67 ( 583469 ) on Thursday March 12, 2015 @02:08PM (#49243209)
    There are two ways of approaching the problem... Get a tool and make your process conform to the tool, or document your process and get a tool that can be modified to support the process. One of these ways works, the other never does.

    That said - most engineering organizations have documented a process and adapted one of many tools to support this process. Sounds like in this case they don't even know what the process is - heck, everyone probably does their own thing so there is likely to not even be a process.

    Try this
    Step 1: Determine how you want issue tracking to work
    Step 2: Get everyone to follow this process without bringing in a tool, your process will change during this step
    Step 3: Document the final process from Step 2
    Step 4: Bring in any tool that can be lightly customized to support the documented process

    Note the hopefully lightly customized part above... Yes there is probably work to do here, regardless of what tool you choose. Most likely you want to pay for the tool that will require the easiest/lightest customization - it will be cheaper than trying to get a tool for free and using a small team to massively customize it.

    • Re: (Score:2)

      by jrumney ( 197329 )
      If the process is undefined to start with, it is better to bring in the tool first and build a process around this. In my experience, when introduction of new tools fails, it is usually because people get fed up fighting a tool that almost but not quite fits their process. The key to success is to make sure the benefits of using the tool are clear to the users and there are no additional headaches associated with its use.

  • Something that also incorporates a wiki might be nice.

    Jira and Confluence integrate well, and have the support of a company and large installed base behind them for future development.

    There will be resistance if it's not really easy to use.

    Joel Spolsky also made a point about formal issue tracker adoption, in that it doesn't have to be all or nothing (Strategy 2) [joelonsoftware.com] from the get-go.

  • I actually just implemented Trac at the company I am with. They were in a similar state for their issue tracking (mouth, emails, sticky note, short bursts of development with potentially very long intervals between software releases). I did a little research and ended up with Trac http://trac.edgewall.org/ [edgewall.org] It comes with a wiki, issue tracking, integrated source control (if you want it), easy searching/reports, plugins, SVN plugin, and it's open source. It is a web-based system so keep that in mind.

    Instal
    • I recommend Trac also. Have used it for multiple projects for years. Haven't used it with mobile devices though, so can't comment on that. Probably works just fine.
  • I have used python based 'Trac'. Bitnami Trac is an easy to install distribution of it:https://bitnami.com/stack/trac.
  • I like Fossil for small projects. Includes tickets and a wiki as well as version control. I don't know how accessible it would be on an iPad but I've played with the Android version a bit. http://fossil-scm.org/index.ht... [fossil-scm.org]

    • I will add that Fossil is a single executable. Just download the executable and copy to a convenient folder/directory. No installation needed.

  • I always use and recommend QuickBase [quickbase.com] for ad-hoc tracking solutions. It is both simple and powerful. It is not free but has a free trial for you to try. It is web-based / SaaS but honestly I would not go any other way in your case. This greatly simplifies management and support, and generally supports any platform (windows, ipad, etc) that has a modern web browser. I have also heard good things about Base Camp [basecamp.com], another web-based solution.

  • mouth-to-mouth?
    With tongue? With good-looking females? Can I work there?

  • I was at Cisco when a group of coworkers tried to implement an email-based ticketing system where the resulting email thread becomes the ticket. A full-featured ticketing system would take up too much time from what little time they had. They never got it to work properly and went back to regular emails to track issues..

    When I mentioned this incident to recruiters, they couldn't wrap their minds around the idea that an email-based ticketing system could save more time than using a full-featured ticketing sy

    • Re: (Score:2)

      by jrumney ( 197329 )
      An issue tracker with email interface can save a lot of time. Not having to log in to receive notification of new issues and being able to quickly comment and close issues by simply replying to an email does save a lot of time. But how do you search existing/previous issues, or check what is outstanding with an email only tracking system? I guess you could send commands and it emails you back, but this isn't exactly efficient compared to a web interface.
  • Setup a synology server and use the community app OS ticket. that would be the easiest thing to do. If you want to go cheaper then setup your own Xpenology server with the same OS ticket.
  • My group utilizes LiquidPlanner, been on it for the past 2 years. Their support is responsive and it seems to scale well. Good email notifications, dashboards, task tracking, and dependency linking.

  • They use mainly Windows and have iPads. I don't like web-based tools...

    Well, why not? If you want to cover that kind of diversity in platforms, you are going to be using a web tool...

  • Github's issue tracking system is damn good, and you can give it a fairly simple, configurable interface via Huboard [huboard.com]. Set up an empty private github repo (private repos are not free but they're very affordable) for your issues, get a huboard (also not free, also cheap-as-chips) account, and away you go.

    I know, I know, you said 'non engineers', and you think I'm mocking you, but that's not the case. While it's true that I'm using this solution to track issues for a technical project (and git repo), I've had

  • Request Tracker by Best Practical is quite powerful, although it can be a real pain in the butt to get installed due to Perl.

    https://www.bestpractical.com/... [bestpractical.com]

    • Re: (Score:2)

      by dskoll ( 99328 )

      I second the Request Tracker recommendation. You need to be a geek to set it up, but not to use it.

      At my company, we started out using it for the tech support staff. Since then, I've expanded it to include requests from salespeople to finance for invoice generation, etc. and it works beautifully.

  • RoundUp or OneAndZero (Score:1)

    by Anonymous Coward

    Roundup is probably the best today - not too complicated, only a couple concepts to remember - handles Web, Email, Command line submissions and searching. http://roundup-tracker.org/docs/features.html (very customizable, python based)

    OneAndZero in the golden GPL days, best web user interface - but like all things "they had to improve and commercialize it" the new versions are awful. Most people run screaming with their hair on fire from it now.. and the people prying version 1.8 from their cooling almost de

  • TaskBoard [matthewross.me]
    Taiga [taiga.io] (leaning towards lightweight project management/"scrummish" stuff)
    PinItToMe [pinitto.me]
    TeamBins [teambins.com]

    Loomio [loomio.org] (decision making tool)

    There are a few more, but these are the ones that come to mind.

  • Now who said governmental analysts were boring? Perhaps this explains why nothing ever gets done? Personally, I prefer mouth to ear communications and will even settle for word-of-mouth, but whatever floats your boat...
  • I implemented youtrack (https://www.jetbrains.com/youtrack/) about 2.5 years ago at the furniture manufacture where I work to manage many different processes within the company. It's easy to get started, customize, and introduce to non-engineers because it's web-based. I highly recommend it.
  • If you can afford it, Jira and WIki from Atlassian (Confluence) are the best out there. If not, i would go with Redmine or Trello. You should also give asana a try. Here's a list that will guide you through what's out there: Freedcamp - Free - https://freedcamp.com/ [freedcamp.com] - Online, doesn't log time directly on the task Velocity - Free and Paid - http://velocity.pm/ [velocity.pm] (Online) Time Tracking Brigthpod - Free (2 Projects) Paid - http://www.brightpod.com/ [brightpod.com] - Specify tasks, log work Asana - Free and Paid - https://as [asana.com]
  • Only someone on slashdot could make speaking to another human being sound so horrible.

Slashdot Top Deals

THEGODDESSOFTHENETHASTWISTINGFINGERSANDHERVOICEISLIKEAJAVELININTHENIGHTDUDE

Close