Fix release milestone communication

[chadwhitacre]

We need a way to communicate our release milestones to internal teams such as docs and marketing. We used to use Jira for this (Asana before that I gather) but now enough teams are on GitHub that the Jira process for this has eroded. What should we do? 🤔

• Internal sheet mapping teams/mgrs to GH/Jira
• Internal doc "The CS guide to product investigations"
• Release milestones in Jira

To Do

• Configure Unito to for GitHub ⇒ Jira (title only, epics)
• Check w/ Compliance re: expanded Unito usage

[chadwhitacre]

Roadmap is not the right word, that's more PM than Eng. What we're talking about here is the release milestone view in Jira, which is designed to communicate product delivery milestones to internal customers—docs, marketing, sales engineering, COPS to a certain extent—so they can prepare to support releases. With some teams moving to GitHub for sprint execution and the change in format of the EPD biweekly meeting (now likely to change again?) the release milestones view has eroded somewhat. Plan is to make a push through existing manager venues to get it updated again.

[chadwhitacre]

Closing for now until there is an obvious step for OSPO to take to help with this.

[chadwhitacre]

I've been tasked by @VladAtSentry with implementing a Release view in GitHub.

I need a view that works. And I need it in 2 weeks. If the jira -> github sync can go the the other way; ok.
What I can't afford is not have the Release View because we are having a ton a different conversations.
So - I need an Release View for all that engineering is going to deliver. If you all can get it done on Github; I am ok. But it must be done by next Friday. I know how we can get it done in Jira....so that is why I am staying with it.
So; we can go to github for the release view, but you are responsible for making it happen; not for facilitating discussion about it. 😛
in 2 weeks I am starting my monthly engineering org execution tracking updates and I need to reference the Release View. I want to put context around what we are working towards, and fit it into an execution narrative.

[chadwhitacre]

Nevermind. We're not ready to have a public board, so this doesn't fit my scope.

[chadwhitacre]

Okay now I'm configuring Unito to support Type: Epic labels into specific Jira projects.

[chadwhitacre]

Calling this good. Internal docs updated new issue forms added for this repo.

[chadwhitacre]

Blech. Reverting in #106. :(