Connect Action Items Log to Project Plan

Hello,

I want to create Actions Item Log.

Our team will also have a project plans. The project plan has planned implementation deliverables but the action items log will be used to capture ongoing actions that come from conversation, issue management, or follow-up (so different tasks). So there is 1 project for the project plan and 1 project for the action items log.

How can I connect the action items log & project plan? For example, I would love to be able to add a tab to the project plan that gives a different link to the action items log but can’t figure that out. Is this possible or is there a better way I should be capturing action items logs that will somehow be linked to the project plan so its more of an implementation/project management hub?

Thanks!

The project containing the plan could have a custom field with Type “Reference” which allows you to point towards action item. Would that work?

Or the other way around, the action item points towards the plan?

@Sarah_Sargent @Bastien_Siebman gave a great suggestion! You can also have a custom field for task type or something along those lines that would say, “This is an action item,” and multi-home the tasks from the action item project to the main project. Any time a task is added to the action item project, it changes that custom field to action item. Then you can have a view in your main project filtered by that task type for action items.

With this custom field, you could also create these action item tasks directly in the project. You could setup a task template for “Action Items” and use that to create any Action Item tasks. Still setup the view in the project that is filtered for Action Items.

@Bastien_Siebman @Ron_Sanga thank you for the helpful suggestions! The challenge is we’re trying to use the read-only versions to share with customers (who don’t have asana licenses) which is why we wanted to go the two different template route (We would share 1 template w/ project plan & 1 w/ action items log). Having them combined on 1 makes it a touch overwhelming. I tested out the custom field & separate list using a filter. Unfortunately all of the section headers still display from the project plan but just show no tasks underneath it.

With all of this, customer facing need, I was really hoping I could make it less cumbersome on the IMs part & at least link the 2nd project (action items log) in the top header of the project plan so it was at least easily accessible from the project plan template.

@Sarah_Sargent thanks for the clarification!

Given the additional information, my recommendation would be to still have everything in one project and then multi-home the planned implementation deliverables in a customer-facing project. This is the project that your customers would be invited to.

Everyone internally is working from a single project, but the customers only have access to things that are shared with them in the customer facing project. Any updates on the planned implementation deliverables would be reflected on both projects since the tasks are multi-homed.

As far as grouping by sections or custom fields, if you click the three dots next to the group selection: you can click on “Hide empty groups”, and this will remove any groups of custom fields or sections that don’t have any tasks listed, based on what’s in the project or what filters you’re using.