My Tasks question

[lpb]

Hi @Tori_Correll,

First, thanks for the nice comment!

I think it will help you a lot to read this help article, at least the initial sections and major ones, and the later Permissions section, though I’m afraid that hasn’t been updated so it’s misleading–it tasks about “Editor and Commenter” but now the permissions are “Project Admin, Editor, and Commenter” so take that with a grain of salt:

Custom fields

Another post that will help is this one I did, and in particular the best practices bullets:

Document Your Organization's Global Available Custom Fields [Best Practice]

You’ll benefit from agreeing upon and documenting (in Asana, of course) your organization’s preferred custom fields for org-wide usage. These should include commonly-used fields, but there’s utility in enumerating all (even more seldom-used) available custom fields you’ve vetted that may come in handy. Perusing this list when you create new workflows and projects may help to remind users of missing or helpful fields they hadn’t consider and will certainly increase consistency. An efficient way…

@lpb

• Use organization-wide (not specific-to-project-only) custom fields… They enable advanced searches based on their values, permit multi-homed tasks to share a common custom field value across projects, and lead to increased consistency.
• Avoid using Asana-provided custom fields directly because they can’t be customized. Instead, one time only, create your own versions of those Asana-provided custom fields that you intend to use…

So in answer to your questions:

• Look at Asana’s Task Status or Task Progress field and then create your own org-wide field(s) as suggested above and you can then add them for use in any projects.
• Because they’re you’re own, not Asana-provided fields, you can freely change the options. (And just changing the options doesn’t ever change the permissions/viewabilility.)

I hope that helps!