hudl / black-mesa Goto Github PK

The problem is on this line. To fix it, Black Mesa should query all pages of repos until there are none left.

It would be helpful if the repositories that will never be used could be filtered out.

If the QA doesn't enter an item (under designer, qa, etc.) and they click 'OK' to the warning that fields aren't filled out, then put 'None' instead of leaving the field blank.

Usually results in duplicate basecamp and black-mesa posts.

Usually when people export the deploys they only are interested in the last 30 days. We should have the option to do both all time and this shorter amount as it will make generating the MOR quicker and easier.

Allow submitting pictures to basecamp posts from Black Mesa (and Alyx) so that they don't have to go to basecamp separately.

Allow searching by date range. Sometimes QA needs to be able to track down a deploy when they only know a general range when it was, so they'd like to be able to search by range.

When exporting data from /api/v1/export the .tsv file includes the entire history – including deleted rows.

This is due to deleted rows not actually being deleted – looks like they are hidden in the /deploys view. If you click on view all, it includes every row.

This is an issue, because the exported data includes duplicated, test and bad entries that have to be cleaned up again after export.

If a Fix is selected let us decide if it is a HotFix or not as not all < 3 day issues are HotFixes and not all > 3 day ones are regular fixes.

On the deploy doc page when adding a person for qa, dev, etc the people in those respective jobs should be bolded and put in the dropdown first.

When editing the projects and components they should show up in alphabetical order

Simplifying the workflow so that only requires two clicks. See attached picture for the workflow.

Bug: Yes/No
Hotfix: Yes/No
New Feature/Enhancement/Task

Please verify that we are not skipping any classification of data by not asking them if it is "behind the scenes"

Other columns appear to update just fine, but trying to add a PM (for example, to a multiverse deploy) and refreshing the page will remove the PM.

When setting the auto-deploy to yes any time you return to the page it will be toggled back to no.

QA would like to be able to put in a PR number for something that does not come from the /Hudl repo. (However they choose which repo... please default it to /Hudl since that is the most common)

The projects listed in the dropdown when manually adding a deploy do not match up with the projects listed at /projects.

We should make sure both of these lists match up. Also, might be worth changing these at this time to match up with our new squad layout. If we do that, the new lists would be:

Media Tribe

Campaigns
Insiders
Content
Profiles

Coaching Tools Tribe

Core
Recruit
Mobile
Basketball
Football
Conversion (not active)
Thick Client (not active)
Volleyball (not active)

Foundation Tribe

Infrastructure
Dev Tools
Front-End Engineering
Platform

No Tribe

Public

I've never done this, so I can't say what the difference should be. Talk to Elizabeth or any of the QA people if you need more info on what they want.

I (Tyson) think the list of projects should be maintained in Mongo so we don't have to push a code change to update them.