Add Asana to the handbook

Why is this change being made?

Asana is going through procurement to become marketing's new task management system, this MR is to add to handbook and update throughout the course of implementation, once a contract is signed.

Why are we adding Asana to our tech stack? We are at times unnecessarily trying to stretch GitLab to do Marketing processes it was not built for, and use cases it will never be used for by our customer base. We have heard Marketing team member feedback that the systems and processes do not support getting our work done effectively (2023 Pulse Survey results). As a result, the Marketing team will start using Asana to improve efficiency, collaboration, and transparency. Asana will integrate with our current technology and processes to streamline inefficient and duplicative workflows. The Marketing team will continue to dogfood GitLab where appropriate and teams whose processes are operating smoothly will not be required to migrate their processes to Asana.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
  • The when to get approval handbook section explains the workflow in more detail
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• Update file index.md

/cc @laurafagan

---