Link Parabol task with already existing GitHub / Jira issue

[BartoszJarocki]

Issue - Enhancement

Currently, we can only create new GitHub / Jira issues. There should be a way to link Parabol task with the already existing GitHub / Jira issue.
Related conversation: https://parabol.slack.com/archives/C836NA350/p1634140455441800

Acceptance Criteria (optional)

• User can link Parabol task with existing GitHub / Jira issue

Estimated effort

• 4 hrs for design explorations

[jordanh]

This really should start as a design exploration, before we get to any coding

@BartoszJarocki do you have a sense of what this might look like? What affordances would we add to our cards?

@ackernaut or @enriquesanchez how many hours would you like to spend on this at some point in the future?

[enriquesanchez]

@ackernaut had already done some explorations around inline integration objects:

More here.

@BartoszJarocki Is something like that what you had in mind?

@jordanh I think 4 hrs would be enough time to solidify these explorations.

[enriquesanchez]

I started exploring this concept and it occurred to me that we may have a broader use case if we instead think of this as "attachments".

I can start by attaching a Github issue to a task, for now—but maybe later on we add the ability to attach documents, images, etc. The mental model is a bit different than the one of linking, but it would open a whole lot more possibilities down the line.

I think this feature will play very nicely with what we have already explored around task details on #5063.

How does that sound to you, @BartoszJarocki and @jordanh?

[enriquesanchez]

Here's a mockup of what I've been exploring:

When a user pastes a link, we can prompt them to paste as link (regular text), or paste as an attachment, which in turn shows a more visual representation of the link's contents, like an embed.

If the user has added the respective integration, the embed will show richer and up to date info, like in the example above. Otherwise we show a more limited view:

We can decide which links we want to support, based on the integrations we support. That said, we don't have to limit these rich embeds to integrations. I imagine we can have rich embeds for things such as Loom videos, websites, etc.

[enriquesanchez]

A few ideas of how other types of URL-based attachments could look:

[enriquesanchez]

Removing attachments and handling when more than one are added to a task:

[enriquesanchez]

Closing in favor of #5942.

@BartoszJarocki Feel free to reopen or add any additional comments or feedback you may have to #5942.