Release 1.7.0

[mickmister]

Summary

• [GH-61]: RHS Support #300
• [issue 194] Closing issues or merge requests does not create an event post with a link back to the project #194 #285
• [GH-262] Merge request approval subscription #307
• [MM-51269] Log errors from telemetry events #363
• [MM51547] Fix telemetry for gitlab and add account connected event #365
• [GH-237] Number of Issues, Notes etc. not correct: API call responds are limited  #366
• fix rudder key secret name #369
• Correctly fetch reviewer for LHS #368
• Remove usage of model.AppError #364
• Increase slash command timeout to 30 seconds #375
• [GH-261] Handle revoked token #308
• [MM-42918] Add debug information for setup wizard #379

Ticket Link

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (226fe9a) 32.94% compared to head (ce0f5ba) 32.94%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #380   +/-   ##
=======================================
  Coverage   32.94%   32.94%           
=======================================
  Files          22       22           
  Lines        4013     4013           
=======================================
  Hits         1322     1322           
  Misses       2560     2560           
  Partials      131      131           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hanzei]

Waiting for #378

[mickmister]

@DHaussermann This release is ready for QA review

[mickmister]

@DHaussermann Heads up that a customer has asked about this release in order to get #378 fixed on their system. Also, we discussed before about getting an RC of this on community. Wondering if this can play a factor in QA review here

[DHaussermann]

/update-branch

[DHaussermann]

@mickmister or @hanzei
Release testing failed because some bugs don't appear resolved. I then realized this branch has no commits added since the original creation. There are fixes in master we're missing.

/update-branch does not seem to work for me in this repo. Can one of you please pull master up?

[mickmister]

@DHaussermann PR is now updated with master

[Kshitij-Katiyar]

@DHaussermann PR is now updated with master

@mickmister @DHaussermann Are you working on the testing of this release or brightscout QA should start on testing the things included in this release?

[mickmister]

@Kshitij-Katiyar Dylan is OOO until next week. Brightscout conducting QA review sounds good to me 👍

[mickmister]

@Kshitij-Katiyar Please take a look at the test cases documented here for release testing the plugin https://github.com/mattermost/mattermost-test-management/tree/main/data/test-cases/plugins/gitlab

The plan is to use a spreadsheet to track verification of the test case passes. I can get you that soon, but please check out the test cases in the meantime. Thanks

[mickmister]

@@Kshitij-Katiyar Here are the documented test cases in Atlassian's UI https://mattermost.atlassian.net/projects/MM?selectedItem=com.atlassian.plugins.atlassian-connect-plugin:com.kanoah.test-manager__main-project-page#!/v2/testCases. You may not be able access, or maybe not make entries for test runs, which is why I suggested to use a spreadsheet.

Here are the same test cases in spreadsheet form
https://docs.google.com/spreadsheets/d/16u7HvW18Cd3pMQSSl5UBck5TOaJSvA8MQn46690RnwY/edit?usp=sharing`

Pasting the above here again as well. This is where the test cases are actually defined
https://github.com/mattermost/mattermost-test-management/tree/main/data/test-cases/plugins/gitlab

[mickmister]

/update-branch

[DHaussermann]

Tested and passed

• Reviewed PRs since last version bump
• Ran through test cycle for GitLab
• No new issues found
• Version correctly bumped to 1.7.0
  LGTM!

Test cases for code preview must still be added to Zephyr but, this does not block the release.