I’ve been evaluating Nozbe for my team using the free accounts and have 2 issues that keep me from upgrading to a paid account.
Shared Project Labels — A MUST
Since this is in the same meta data of the project, why don’t they get shared along with all the other parts of the project.
Shared Contexts — Could be worked around but would be a huge feature.
this is a bit more complicated as what if you don’t have a context, it would have to be created, etc… what if you have a similarly named context but another team member didn’t so they created a new one for them that was “waiting on client” and you have “waiting for client”... all that can be handled by the team themselves… no reason that should hold up a very important feature.
If these are already possible in a paid family account or higher… I’m ready to subscribe. I can see that these might not work so well with regular project sharing… but a linked team account MUST be able to have things like shared/synced labels so when there are 40 projects going on we can manage them all as a team.
Thank you for creating such a great tool…
-Product VideoCast
Comments:
Thank you for your e-mail response.
For other users, the workaround was to add labels [bracketed] on projects and contexts [bracketed] on tasks when those need to be shared.
Won’t really work for us (as far as the labels go), but in a lot of situations it is a good workaround.
I have though of one more workaround and it is to use the 1st comment in action to pass the context around. In case of projects… you can always add the label into the description. ... I believe this might solve your bracket issue ;-)
Delfina / Perry — just wanted to give this functionality request a bump. I just returned to Nozbe b/c of the release of the bookmarklet, signed up for a team account for my family and was shocked to realize that none of the meta-data carries over. The logic should be that if a project is shared, the meta data carries over. While there may be slight differences in how users manage their labeling system for non-shared projects, I don’t know that you absolutely need to build functionality to rectify that problem, at least for the initial release.
+1 labels for sure
@ Rebecca,
Please note that Perry is not a representative of Nozbe. As for me, all I can say this that this feature is on the planned list. There are some concept problems the tech has been having with it, but it is by no means being disregarded. We do want to improve Nozbe to accommodate for needs of multi-user accounts, such as shared contexts or different levels of access to shared projects.
Definitely need to be able to share labels and contexts. No data should get stripped off when sharing a project
What is the ETA for getting this completed? This single enhancement will certainly move the solution to a different level among the competition when working in group environments. We are anxiously waiting this arrival.
Daryl I wish I could give you an approximate date, but I simply am in no position to do so. The internal rumor has it that there is a big update to sharing ect. coming within a month, but I do not have yet the list of proposed features.. the only thing I know for sure is that the notification are coming in the line with that.
+1 for shared contexts and labels from me – almost a go/no-go question for running teams. meeting-agendas etc get so much easier with contexts, and much much more
I upgraded to the multiuser account because I am a fan of the book. This feature is urgently needed to make Nozbe better.
+10 for shared contexts and labels. I thought Nozbe was going to be perfect for our small staff and purchased the family plan. I was horrified when we saw those two weren’t shared. Any more “rumors” on an ETA since “coming within a month” was three months ago?
+ million? :) Nozbe is great, this would be greater!
@Delfina, any word if this is on the end of year teams update?
@Christine. Tentatively yes, but please do not put my head on chopping block if for some reason it won’t be. The plans change constantly depending on technicalities behind.
Crucial feature. There should be a “bank” of labels & contexts that all members of the team can add to (whether it’s attached to an active project/task or not) and says available for use until an administrator or authorized team member deletes it.
*stays available.
@Gloria… thank you… this is a great hint.. making a bank of labels and context…
Copyright © 2012 apivision.com all rights reserved
GTD® and Getting Things Done® are registered trademarks of the David Allen & Co.
English
日本語
Nederlands
Español
Deutsch
Français
Polski
Hello,
As per my email response. Those will become features, as there are many multi-users that seem to need those two as features. The teach is working on it currently. Meanwhile I can only ask you to try the workarounds I have provided you with in the email.