Questions and Answers
What is the recommended solution to provide support partners quicker access to documented requirements for CWOW issues?
What information should be included in each Confluence page for a feature set?
What is the project and issue type for which the support partners need quicker access to documented requirements?
Study Notes
- Support partners need quicker access to documented requirements for CWOW issues.
- Currently, they lack visibility into the history of each feature set.
- A solution is to provide Confluence pages for each functional lane that groups all versions of a feature together.
- The pages should include Jira IDs, feature title, fixversion, link to OneView exports, and feature description.
- Steps to achieve this include gathering Jira IDs, compiling a list of features, grouping them into feature sets, and creating Confluence pages using a template.
- The Jira query for each page should include the appropriate Jira IDs.
- The project is CWOW and the issue type is feature.
- Display options should not need to be changed.
- The page title should be the feature title without CWOW identifiers or version numbers.
- Repeat the process for each feature set until complete.
Studying That Suits You
Use AI to generate personalized quizzes and flashcards to suit your learning preferences.
Description
Are you familiar with the best practices for providing support partners with quick access to documented requirements for CWOW issues? Take this quiz and test your knowledge on the solution of creating Confluence pages for each functional lane that groups all versions of a feature together. Learn about the steps involved in gathering Jira IDs, compiling a list of features, grouping them into feature sets, and creating Confluence pages using a template. Challenge yourself to master the Jira query for each page and learn how to repeat the process
