Sticky header component for issuables

Release notes

Problem to solve

As part of implementing #241671 (closed), we will create a sticky header component for incidents. Longer-term, we'd like the same sticky header component to apply to all issuables. How might the component we're creating for incidents need to be modified to fit all the required use cases?

Additional discussion here: #241671 (comment 430506349)

Intended users

User experience goal

Proposal

Further details

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references