Merge pull request #582 from zapier/closing_issues_docs

[PARTOPS-951] Add instructions on how to close issues after promotion

docs/_manage/integration-performance/user-feedback.md

@@ -40,7 +40,19 @@ Problems with your public integration, authentication and API calls will be logg
 
 - Allocate ongoing resources in your team’s product roadmap for the maintenance of your Zapier integration to avoid surprise work or gaps in functionality. Consider a [Zapier Expert](https://zapier.com/experts/matchmaking) to help you fix one-off bugs or maintain your integration.
 
-## 3. Consider Zapier Issue Manager
+## 3. Close resolved issues
+
+- Bugs and feature requests require review and verification from Zapier's Support team before they can be closed. When an issue is closed, email notifications are sent out to all affected users on the issue, notifying them of the update.
+
+- Whenever a new version of your integration is promoted via the UI, you'll be prompted with a changelog form asking you to identify which feature requests or bugs were resolved and to provide a user-facing description of the changes. Issues identified in the changelog will automatically be queued for review by our Support team and closed once resolution is confirmed. Promoting via the CLI doesn't currently support changelogs.
+
+![Changelog Form with Issues](https://cdn.zappy.app/8afba17ecfb25faf6b87597e2cd54387.png)
+
+- You can also request issues to be closed manually by selecting one in the "Bugs & Feature Requests" tab of the developer platform, and leaving a comment to our Support team that the issue has been resolved. Provide info on what version number the fix is on, how to test the updates, and any other helpful callouts.
+
+- Once an issue is reviewed, it will either be closed or responded to with follow-up questions and feedback.
+
+## 4. Consider Zapier Issue Manager
 
 - If you prefer syncing and managing issues from your own issue-tracking tools (such as Jira or Trello), create Zaps using Zapier Issue Manager.
 
@@ -74,7 +86,7 @@ Problems with your public integration, authentication and API calls will be logg
   use-this-zap="show"
 ></zapier-zap-templates>
 
-## 4. Monitor integration insights
+## 5. Monitor integration insights
 
 - [See all the metrics tracked](https://platform.zapier.com/manage/integration-insights) in this table, or access them for any integration you are an Admin or Collaborator on from the _Dashboard_ tab of the Platform UI. Insights include important data on both the integration's growth and usage, such as monthly active users, retention rates, and Zap usage by triggers and actions.
 

docs/_manage/versions/promote.md

@@ -13,11 +13,8 @@ After your integration has entered the beta or public status, you can set a new
 1. Log into the [Platform UI](https://zapier.com/app/developer).
 2. Select your **integration**. 
 3. In the *Manage* section in the left sidebar, click your **Versions**.  
-4. On your version you want to promote, click the **three dots icon** <img style="vertical-align: middle;" src="https://cdn.zappy.app/7ff6381b55b013ebfc2bdda0e4662676.png" alt="navMoreHoriz icon" width="24">.
-5. To make the chosen version the public and default version, click **Promote**.
-
-
-![Platform UI Versions tab, showing where to find the three dots icon](https://cdn.zappy.app/2ee11c82946187818a9622c4b4bf65bc.png)
+4. On the version you want to promote, click the **three dots icon** <img style="vertical-align: middle;" src="https://cdn.zappy.app/2ee11c82946187818a9622c4b4bf65bc.png" alt="navMoreHoriz icon" width="50%"> and **Promote**.
+5. Fill in the [changelog form](https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues) and click **Promote**. Selecting specific features added and bugs fixed will automatically queue up the issue(s) to be reviewed by our internal team for closure.
 
 > **Note**: If you have a private integration, you will not see the *Promote* option. Instead, you can [share your new version](https://platform.zapier.com/manage/share-integration) with users.
 

docs/_reference/cli.md

@@ -412,6 +412,8 @@ Promote an integration version into production (non-private) rotation, which mea
 
 Promotes are an inherently safe operation for all existing users of your integration.
 
+After a promotion, go to your developer platform to [close issues that were resolved](https://platform.zapier.com/manage/user-feedback#3-close-resolved-issues) in the updated version.
+
 If your integration is private and passes our integration checks, this will give you a URL to a form where you can fill in additional information for your integration to go public. After reviewing, the Zapier team will approve to make it public if there are no issues or decline with feedback.
 
 Check `zapier jobs` to track the status of the promotion. Or use `zapier history` if you want to see older jobs.