Hi there,
I have project 1 and project 2 (board view). I would like to make sure that when I add a task to one
column in project 1 it is also added AUTOMATICALLY to one column in project 2.
Is this possible ?
Many thanks
Hi there,
I have project 1 and project 2 (board view). I would like to make sure that when I add a task to one
column in project 1 it is also added AUTOMATICALLY to one column in project 2.
Is this possible ?
Many thanks
Hi @Sandra_Fernandes-Mac. Unfortunately, there isnât a way to automatize this process in Asana; that said, when creating a task in âproject 1â, you can easily add it to one column in project 2 using the multihome function (How to Complete Task Fields in Asana | Product Guide âą Asana Product Guide).
Hey - ping on this one. Has this functionality been developed yet? My use case is connecting my own kanban board to a team kanban board and thereby allowing me to structure my tasks independently of my team while keeping transparency between my tasks towards the rest of the team. I.e. I would have 4 categorical columns in my personal board that would feed into 1 column in the team board (consisting of all my tasks). Perhaps youâd suggest another approach?
Thanks!
David
@David_Löfgren, If you have a Business plan, you can now write custom Rules for this:
Larry
Hey @lpb,
Actually I believe using Asana rules wonât work for this because they donât fire as the result of automation-made changes; itâs discussed here:
However, Flowsanaâs rules donât have this limitation, so I know this can be done using Flowsana rules.
@David_Löfgren, because sections are specific to projects and are not shared between projects, you canât accomplish this directly.
So, if you want to use my Flowsana integration to accomplish it, what you can do is use a custom field (you can also use a tag) to in essence link the two projects together, and then create rules in each project.
I.e. in Project A you create a rule like "If task gets moved to Section âIn Progressâ, set the value of custom field âStatusâ to âIn Progressâ. Then in Project B, you create a rule like "If value of custom field âStatusâ gets changed to âIn Progressâ, move the task to the âIn Progressâ section.
Note that you have to make sure the custom field is a global one; that is, it lives in your organizational custom field library.
I should also note that you can add your vote for Asana to have this âsync columns between projectsâ capability here:
Thanks for your replies, much appreciated. I simply wanted to âexportâ all tasks from one project into a specific section in another and that seems to work well by using the rule âTask added to this project â Add to another projectâ.
My next inquiry is around the Field customization as this seems to be âimportedâ from the project to where the tasks will be directed based on the rule mentioned above, which is great. Itâs just that I dont get the fields to show up as âlabelsâ on the specific task in the kanban view and instead I have to go into the âdetailed planeâ to the right to see values such as priority etc. Is there a way to have them being shown ON the âtask cardâ instead?
@Phil_Seeman, I was suggesting a set of one-way rules as @David_Löfgren alluded to which wouldnât encounter the problem you mention, though of course thereâs extra flexibility with Flowsana.
@David_Löfgren, Custom Fields do appear in Board View Cards for me; maybe you can be more specific and include screenshots of what you mean so itâs more clear to me or maybe Phil understands?
Larry
@David_Löfgren, custom fields show up for me as well on task cards in board view. As @lpb says, if you could post a screenshot indicating what youâre missingâŠ
Thanks for looking into this. Set-up explained and picture attached:
Hi @David_Löfgren,
So, two things to note:
Regarding the project on the right in your screenshot - youâre 100% correct, the custom field values appear on the card in Board view but not the labels. Iâm sure that was done so as to take up less space and not make the cards bigger.
Regarding the custom field values not showing on cards in the project on the left - Iâm sure this is because those custom fields are project-specific custom fields that are specific to the right-hand project. Theyâll need to be global (i.e. in your organizational custom fields library) for them to show on multiple projects.