Hi Team! Are you working through an incident and lose track of all of the relevant links? Perhaps they are buried in the comments throughout your incident? We'd love to hear from you.
We recently built Linked Resources on GitLab Incidents and are looking for your feedback! Give Linked Resources a try in the Tanuki project and add you feedback to this issue.
Design: It would be nice to have the favicon next to a link. During an incident, scanning information is even more critical, and the favicon from the external link would help the user find the link visually much faster.
Functionality: I don't see adding a linked resource showing up in the activity log. Is this forthcoming? Its not critical, but when we put together timelines of what happened, who did what, a robust activity log helps us analyze our response. The activity log also helps the IMOC verify that people are working on things, particularly if things are happening async.
Dogfooding: I do not see this picking up usage without integrating it into Woodhouse. Is there an MR to populate these values from Woodhouse when an incident gets declared?
@sethgitlab - Thanks for taking the time to take a look a linked resources! I have a few followup questions.
Design - Right now we've just added the favicon for Zoom. What would be your top 5 links that you would like/expect to see favicons for?
Functionality - Adding a linked resource to the activity log is forthcoming. @rkadam3 do we have an issue for this already? I didn't see one in this epic Linked Resources (&3994). If there isn't an issue yet, I can create one.
Dogfooding - Resource Links will be incorporated into our first iteration of the Incident Management Slack App that will eventually replace Woodhouse. The designs for the Slack App can be viewed in our 15.4 kickoff video (2:00-4:50)
@abellucci
For top links, I think they generally fall into a few categories (off the top of my head).
Video Communication: Zoom (for GitLab), but customers may use Hangouts, Teams, etc.
Text Communication: Slack
Documents: Google Docs or Google Sheets, customers may use Word Docs
Version Control: GitLab (obviously ), but customers could be using
Github, BitBucket, etc. In some cases GitLab may refer over to GitHub if we are using a component or piece of software hosted there.
One of the reasons some of these may be difficult is that url will be custom for each customer. For example, Gitlab doesn't use sentry.io we use https://sentry.gitlab.net/.
Top 5: I would boil down to
Zoom, Slack, Google Docs, Gitlab, HackerOne.
To make favicons really scalable, I think you would need to dynamically retrieve them. Trying to hardcode 5 favicons will work for an MVC, but it will probably show its limits very fast.
Thanks for the detailed list of favicons @sethgitlab! I went ahead and created a separate issue for this work; #371210 (closed). I omitted the favicons you suggested Version Control and Issues as a first pass. We'd prefer if users were using GitLab and they can still add the links, there just won't be a favicon. Additionally, GitLab issues can still be related to one another through Linked items, even in incidents.
I like the "Linked Resources" concept. One thing to watch out for is that the Incident Zoom link contains a password that we may not want to be publicly accessible.