We tried using hubfly (www.hubfly.com). We checked out their website and found more features than we wanted. We took a demo and told them that we could not afford more than $2,000. We had them customize it for us as well. It has been paying off (not sure about the long term results): we have a good internal communication tool that helps engage our employees.
Thanks for the reply.
We currently use JIRA for bug tracking. What we are looking for is a tool like userback(https://www.userback.io/) for SF application.
This way user can capture bugs along with the relevant details (screenshots,videos, logs etc) and the bug gets created automatically in JIRA
Well, how about Easy Projects. You didn't specify the acceptable budget so... But it has the flexible price system, that adjusts to the functionality chosen. Pretty neat, isn;t it? Here is a link https://www.easyprojects.net/basecamp-alternative/ for you to check it out. If you like it great to be of assistance. If not, it' s not a big deal, maybe somebody else will find this useful
Thanks for the reply.
We are currently tracking bugs in JIRA. What we are looking for is something similar to Userback (https://www.userback.io/) for SF Applications.
Something like this would enable user to capture the issues (screenshots, videos, logs) and this would automatically show up in JIRA as bugs.
My personal wiki is a study and reference tool, so it's structured by subject/vendor (Microsoft -> System Center -> Operations Manager)
My version of the work wiki is structured by customer, then drill down to different sections and eventually individual pages (CustomerA -> Servers/Devices -> ServerA). Unfortunately this project was shutdown as we were ready to go into testing, so I have no idea how well it works in a production environment.
If I may, I recommend looking into Tiki Wiki. It's FLOSS and relatively easy to figure out if you like reading documentation. The Structured Wiki would be your primary feature. For making sure people see changes, you could use the Newsletter feature for distributing changes by email. Or, if you want to be more passive about it, you could create a tracker for important changes then put a widget on the home page of the Wiki displaying the most recent item(s) submitted to the tracker. Or you could do both, saving newsletters to a tracker and then publishing that tracker to the wiki home page.
You mean a ready to go package supporting all this that you can host yourself? Sounds like you're looking for something like a Content Management System. There are bunch out there, but they will require a good level of customizing.
Tiki Wiki is my go to CMS. It could do what you're looking for, but it does require a decent amount of time to learn about the features you'll need. If you have a budget for this, you could find a third party consultant to build it for you. There are a number of companies globally who specialize in Tiki.
we adapted the built in settings to our team. Mavenlink itself cant be customized, at least not status of the project, but it have about 6-8 settings per current state, from " in proposal" to "project completed" the paid version has a very extensive reporting and even personnel scheduling sections. Overall it's pretty usefull, not prefect, I wish it had some more trello type cards for watching a project easier, But, it's a big step from our last tool smartQ http://www.getsmartq.com/