This looks great. Quick question, is it possible to automatically apply the same rule to all new projects that you create on Asana?
We rely on sprints and for each sprint, we create a new project. Having to do this every 2 weeks seems a little time-consuming (I know that you can copy rules from one project to another).
This seems really great for our team. Is this a rule that you have to create in each project or would the task ID be for your whole workspace?
Are subtasks numbered or can you exlude those?
You do have to create the rule in each project - all Flowsana rules, like all Asana rules, are project-based.
Flowsana’s unique IDs are unique across the whole workspace, though.
Also note: although the rule needs to be in each project, Flowsana does have an option which copies all Flowsana rules from one project to another - so you don’t actually have to build the rule from scratch in each project, you can just copy it.
Has anyone went one step further and used Flowsana for Unique ID application for tasks, and then has integrated further with Github? The current GibHub + Asana integration is cumbersome. I cannot find a manner in which the task in Asana gets automatically updated with the status from GitHub. Thanks and looking forward to seeing if there are any solutions to this. The widget showing the status from Github in the Asana task is not automated enough for my team as we still need to manually update the task status.
thank you @Phil_Seeman - just seeing this now. Wanted to reconfirm re the question above, are task IDs also get applied to subtasks, or is this only working for high-level tasks?
@Phil_Seeman thanks for clarification. Is it possible to concat with some prefix so as to transform it to format in-line with our requirement e.g. TID_XX_0001, etc. ?
Yes, definitely. Our unique IDs are part of our Variable Substitution feature, meaning that to include a unique ID anywhere - in a task name or a text custom field, for example - you just put {task.ShortId} in combination with any other text or variables.
So for example:
TID_XX_{task.ShortId}
Or if XX represents some value like, say, a project code, then perhaps:
TID_RP_{task.ShortId}
You can even combine multiple variables, for example:
TID_{task.Project Code}_{task.ShortId}
That is indeed helfpul @Phil_Seeman. A challenge here is that since its a counter so the ID generation is TID_XX_1, TID_XX_2,…, TID_XX_10, … TID_XX_99, TID_XX_100, … and so on. Is there a way to prefill it with 00s so as to make more standardized. e,g, TID_XX_001, TID_XX_002,…, TID_XX_010, … TID_XX_099, TID_XX_100, … so on…