search

Azure / azure-sdk-tools

Tools repository leveraged by the Azure SDK team.
MIT License
109 stars 166 forks source link

UI - Create a release plan feature - updates to support identifying release scenarios (i.e. APEX vs non-APEX) #6262

Open ladonnaq opened 1 year ago

ladonnaq commented 1 year ago

Requirement: When user's create a release plan we do not know if the work they are doing is associated with an upcoming product launch that is in scope for the APEX launch readiness program or if the work they are doing is for new functionality that is not in scope for APEX. All release plans for APEX require signoffs in S360 for the APEX launch readiness launch criteria (S360 KPI action items). So we need to clearly understand from the Release Plan ADO work items if the release plan is APEX or non-APEX.

UI changes

image image

Data and conditional logic Product Details

  1. After product is selected, check the value of the isAPEX field in the epic type = product.
    1a. If isAPEX =no, then do not display the questions for isAPEX, isExtension, and the APEX lifecycle milestone drop-down box. Update the isAPEX ADO field in the release plan value to "no". Proceed to step 5. 1c. If isAPEX = yes, then proceed to step 2.
  2. Display the first APEX question "Will this release plan be used to complete requirements for Azure Product Excellence (APEX)?" yes/no 2a. If answer is "yes" update the isAPEX ADO field in the release plan work item value to be "yes". Proceed to step 3. 2b. If answer is "no" update the isAPEX ADO field in the release plan work item value to be "no". Proceed to step 5.
  3. Is this release plan to complete an APEX exception? yes/no 3a. If yes, then update the isExtension ADO field in the release plan work item value to "yes". Proceed to step 4. 3b. If no, then update the isExtension ADO field in the release plan work item value to "no". Proceed to step 4.
  4. Display drop-down for use to select "Target APEX lifecycle milestone". The Release Plan Target Lifecycle ADO field in the release plan work item value is set to the value selected by the user. Proceed to step 5.
  5. User selects release plan type from "Release Plan Type" drop-down box.

API Details

  1. Update API Spec Type ADO Field in the API Spec work item with the value selected by user.
maririos commented 12 months ago

This issue is to unblock most of the Data plane teams to use the Release Planner

maririos commented 11 months ago

Given how the priority right now is to get the Dashboard feature complete, I am moving this issue to backlog

ladonnaq commented 6 months ago

@maririos Once this issue is resolved - https://github.com/Azure/azure-sdk-tools/issues/6638, then hopefully all service partners will be able to find the most closely related product in the drop-down box and create a release plan. So this requirement should be focused on adding a question to confirm if the work is for an upcoming product launch that is in scope for the APEX launch readiness program or is the work for new functionality that is not in scope for APEX. I will modify the description and find some time in Jan 2024 to meet with @JonathanCrd to discuss.

ladonnaq commented 1 month ago

FYI @maririos - I completed these tasks today.

  1. Add picklist custom ADO field to the release plan work item. ADO field name = " isAPEX" with string picklist values of "yes" or "no". (La Donna)

  2. Release Plan type picklist values simplified: Private Preview, Public Preview, and GA. Add to existing picklist values, do not remove any values. (La Donna)

ladonnaq commented 1 month ago

@ckairen @maririos I have added screenshots of suggested changes to UI and data/conditional logic associated with the UI changes.

maririos commented 1 month ago

@ladonnaq foolow up questions: