Hi All,

We think that each task can be only in progress, not in progress or completed but true – not in progress task can have a clarification sub-status like ‘waiting for a feedback’ or ‘postponed’ and we do consider adding sub-statuses in the future. Things like ‘Testing’, ‘Review’ – task lists can be used to handle. A task in ‘Testing’ task list will still be in progress, not started or completed because if you set it as status you will never know if actual testing phase not started, in progress or completed. To handle this in Kanban view we plan to allow to switch Kanban view to show columns as task lists in addition to by status available now. Hope it helps what is planned and what to expect.

Summary:
- add substatuses (allow to edit them)
- Kanban columns either per status+sub-status or task list

Please email your Freedcamp account email if you want to be invited to internal Freedcamp discussion to define a roadmap for this feature in Freedcamp and work with the Freedcamp team.

Cheers,
Igor

Hi All,

We will be starting it as soon as we push English locales to http://translate.freedcamp.com for community to translate and launched white label (both improvements were sponsored).

Regarding Last Tim’s comment. I see progress tracking to be totally flexible from no tracking, as now, to estimate vs worked hours and all in between.

I see it as a project creation wizard, where you create your N’s project and select how you want to track progress and have an option to say ‘Use these same settings for all my future projects’. Once set, Freedcamp will not ask you again but prompt you to a) invite people and b) show what project settings will be used, giving you a chance to jump in and change defaults.

This way we save your time, if you use same settings for all projects. Those who do not want to track progress at all will see no difference. Those who want to track as % or worked time vs estimate will also be able to do so.

Cheers,
Igor
CTO Freedcamp

Hi All,

Since everyone here is a software developer – let’s get serious about it → define scope, count how many people can contribute and either collect money directly as a donation or go Kickstarter just to add this extension for you.

Other option – one or few business sponsors who already use Freedcamp and need this extension – http://blog.freedcamp.com/2015/11/25/sponsor-feature-development-get-freedcamp-life-time-free-with-unlimited-storage/ – you will get a great deal of paid services free in return – we promise.

We know that a lot of software developers use Freedcamp to talk to clients and use other tool to manage software development process and we understand pains of using two systems.

We would love to but have no resources now to open Freedcamp to allow you guys create extensions (both free and paid) and offer them on our marketplace like SalesForce or Apple do.

It is a part of our vision but we haven’t found that investor yet and we are not big enough now to launch an open platform.

Cheers,
Igor

We have two use cases here.

1. Making is super easy to work with clients. Clients can see only Discussion and Tasks which specifically marked as visible to them. Rest is not visible to them

2. Allowing true privacy – concept described by Caroline. Once this mode is enabled users can create private tasks and decide who they want to share it with.

@Caroline – I assume project and project group administrators should be able to see private tasks. Right?

Probably we should move Private Tasks and Private Discussions into a separate add-on which is not available by default.

We have requests for private tasks and we have requests for disabling privacy – when a teacher in a school does not want students to create private tasks at all.

I assume functionality similar to Private Discussions we already have in Freedcamp is what you are after.

At this stage I am not even sure how to implement it best way. We do not have concept of ‘client’ in Freedcamp. We will need to add a special attribute to project teams which will say – this team is ‘client’ and once you set this attribute to a team you can create a task which is visible to clients. If not ticked – not visible to them. On screenshot (https://www.dropbox.com/s/rp9sij4usvf6x7i/Client%20Teams.png?dl=0) set attribute shown in black box which will tell Freedcamp – people in this team are clients. This way you can have multiple clients teams in the same project with different permissions.

Let me know what you think please.

Cheers,
Igor