ADO Wiki, Boards & Plans

​

Introduction

• Azure Wiki (ADO Wiki): Collaborative wiki service for creating and managing project documentation, knowledge bases, release notes, and meeting minutes. Provides version-controlled repository for team documentation.
• Azure Boards (ADO Boards): Work tracking and project management service for planning, organizing, and tracking tasks, user stories, bugs, features, and epics. Includes agile planning tools, customizable dashboards, and workflow automation.
• Azure Test Plans (ADO Test Plans): Comprehensive test management solution for planning, executing, and tracking software testing. Enables test plan creation, test suite organization, test case authoring, and test execution tracking.

​

Toolkit’s Account Setup and Configuration

​

Account Setup

1. Visit Azure DevOps: Navigate to https://azure.devops.com/
2. Start Free or Sign In: Click “Start free” to create a new organization, or “Sign in to Azure DevOps” for existing accounts
3. Create Organization: Follow prompts to set up your organization (provide name, select hosting region, optionally link to Azure account)
4. Verify Email: Confirm your email address if prompted by clicking the verification link
5. Enable Basic Subscription: Verify Basic subscription is enabled (typically enabled by default for new organizations). This grants access to Boards, Repos, Pipelines, Test Plans, and Artifacts
6. Add Users (Optional): To grant access to team members:
   • Navigate to https://dev.azure.com/{YourOrganizationName}/_settings/users
   • Click “Add users”
   • Enter user’s email address or Microsoft account
   • Select “Basic” access level
   • Choose relevant project(s)
   • Click “Add”
7. Configure Project Permissions (Optional): To ensure users have project access:
   • Open “Project settings” (bottom left)
   • Select “Groups” under Security
   • Add users to “Project Valid Users” or relevant group
8. Verify Access: Confirm “Boards”, “Wiki”, and “Test Plans” appear in the left sidebar

​

Generate a Personal Access Token (PAT)

1. Log in to Azure DevOps: Access your Azure DevOps organization by navigating to https://dev.azure.com/ and logging in with your credentials.
2. Access User Settings: Click on the User settings icon in the top right corner, next to your profile picture. From the dropdown menu, select “Personal access tokens”.
3. Generate New Token: Click the ”+ New Token” button to create a new PAT.
4. Configure Token Details: In the “Create a new personal access token” panel, configure the following:
   • Name: Enter a descriptive label (e.g., “ELITEA Integration” or “ELITEA ADO Access”)
   • Organization: Select “All accessible organizations” or choose specific organizations
   • Expiration: Set an expiration date for enhanced security
   • Scopes: Grant only the minimum necessary permissions
   !!! tip “Token Scopes” Minimal Scopes for Common Use Cases:
   • Custom Defined - Select to manually choose granular scopes
   • Work items:
     • Read (To read work item details)
     • Write (To create or update work items - only if needed)
   • Wiki:
     • Read & write (For full wiki access)
     • Read (If agent only needs to read wiki content)
   • Test Management:
     • Read (To read test plans and cases)
     • Read & write (To create or update test plans - only if needed)
   • Additional Scopes for Specific Functionality (Grant only if needed):
     • Build (For Azure Pipelines builds interaction)
     • Release (For Azure Pipelines releases interaction)
5. Create Token: Click the “Create” button to generate your PAT.
6. Copy and Store Token: Copy the generated token immediately - this is your only chance to see it. Store it securely in a password manager or ELITEA’s Secrets feature.

​

System Integration with ELITEA

​

Step 1: Create Azure DevOps Credentials

1. Navigate to Credentials Menu: Open the sidebar and select Credentials.
2. Create New Credential: Click the + Create button.
3. Select Azure DevOps: Choose Ado as the credential type.
4. Configure Credential Details:

   Field	Description	Example
   Display Name	Enter a descriptive name (e.g., “Azure DevOps - Team Project Access”)	Azure DevOps - Team Project Access
   ID	Unique identifier for the credential	Auto-populated from the Display Name
   Organization Url	Enter your Azure DevOps organization URL (e.g., https://dev.azure.com/YourOrganization)	https://dev.azure.com/MyCompany
   Project	Enter your Azure DevOps project name (e.g., MyProject)	ProjectAlpha
   Token	Enter your PAT or select a secret containing your PAT	ghp_1234...

5. Test Connection: Click Test Connection to verify your credentials are valid and ELITEA can connect to Azure DevOps
6. Save Credential: Click Save to create the credential. It will be available in the Credentials dashboard for use in toolkit configurations.

​

Step 2: Create Azure DevOps Toolkits

​

Azure DevOps Wiki Toolkit

1. Navigate to Toolkits Menu: Open the sidebar and select Toolkits.
2. Create New Toolkit: Click the + Create button.
3. Select Azure Wiki: Choose Azure Wiki (ADO Wiki) from the list of available toolkit types.
4. Configure Toolkit Settings:

   Field	Description	Example
   Toolkit Name	Enter a descriptive name for your toolkit	ADO Wiki - Documentation Manager
   Description	Optional description of the toolkit’s purpose	Toolkit for managing project wiki documentation and knowledge base
   Credentials	Select your Azure DevOps credential	Azure DevOps - Team Project Access
   PgVector Configuration	Select a PgVector connection for vector database (required for indexing tools)	elitea-pgvector
   Embedding Model	Select an embedding model for text processing and semantic search	text-embedding-3-small
   Default Wiki Identifier	Default Wiki Identifier (Wiki ID or wiki name). If provided, this identifier will be used when tools are invoked without explicitly specifying a wiki identifier.	ProjectWiki

5. Enable Desired Tools: In the “Tools” section, select the checkboxes next to the specific Wiki tools you want to enable. Enable only the tools your agents will actually use to follow the principle of least privilege
   • Make Tools Available by MCP - (optional checkbox) Enable this option to make the selected tools accessible through external MCP clients
6. Save Toolkit: Click Save to create the toolkit.

Available Wiki Tools:

​

Azure DevOps Boards Toolkit

1. Navigate to Toolkits Menu: Open the sidebar and select Toolkits.
2. Create New Toolkit: Click the + Create button.
3. Select Azure Boards: Choose Azure Boards (ADO Board) from the list of available toolkit types.
4. Configure Toolkit Settings:

   Field	Description	Example
   Toolkit Name	Enter a descriptive name for your toolkit	ADO Boards - Work Item Manager
   Description	Optional description of the toolkit’s purpose	Toolkit for managing work items, bugs, and user stories
   Credentials	Select your Azure DevOps credential	Azure DevOps - Team Project Access
   PgVector Configuration	Select a PgVector connection for vector database (required for indexing tools)	elitea-pgvector
   Embedding Model	Select an embedding model for text processing and semantic search	text-embedding-3-small
   Limit	Default ADO boards result limit (can be overridden by agent instructions)	5

5. Enable Desired Tools: In the “Tools” section, select the checkboxes next to the specific Boards tools you want to enable. Enable only the tools your agents will actually use
   • Make Tools Available by MCP - (optional checkbox) Enable this option to make the selected tools accessible through external MCP clients
6. Save Toolkit: Click Save to create the toolkit.

Available Boards Tools:

​

Azure DevOps Test Plans Toolkit

1. Navigate to Toolkits Menu: Open the sidebar and select Toolkits.
2. Create New Toolkit: Click the + Create button.
3. Select Azure Test Plans: Choose Azure Test Plans (ADO Test Plan) from the list of available toolkit types.
4. Configure Toolkit Settings:

   Field	Description	Example
   Toolkit Name	Enter a descriptive name for your toolkit	ADO Test Plans - QA Automation
   Description	Optional description of the toolkit’s purpose	Toolkit for managing test plans, suites, and test cases
   Credentials	Select your Azure DevOps credential	Azure DevOps - Team Project Access
   PgVector Configuration	Select a PgVector connection for vector database (required for indexing tools)	elitea-pgvector
   Embedding Model	Select an embedding model for text processing and semantic search	text-embedding-3-small
   Limit	ADO plans limit used for limitation of the list with results	5

5. Enable Desired Tools: In the “Tools” section, select the checkboxes next to the specific Test Plans tools you want to enable. Enable only the tools your agents will actually use
   • Make Tools Available by MCP - (optional checkbox) Enable this option to make the selected tools accessible through external MCP clients
6. Save Toolkit: Click Save to create the toolkit.

Available Test Plans Tools:

​

Testing Toolkit Tools

1. Select LLM Model: Choose a Large Language Model from the model dropdown in the Test Settings panel
2. Configure Model Settings: Adjust model parameters like Creativity, Max Completion Tokens, and other settings as needed
3. Select a Tool: Choose the specific Azure DevOps tool you want to test from the available tools
4. Provide Input: Enter any required parameters or test queries for the selected tool
5. Run the Test: Execute the tool and wait for the response
6. Review the Response: Analyze the output to verify the tool is working correctly and returning expected results

​

Step 3: Add Azure DevOps Toolkits to Your Workflows

​

In Agents:

1. Navigate to Agents: Open the sidebar and select Agents.
2. Create or Edit Agent: Either create a new agent or select an existing agent to edit.
3. Add Azure DevOps Toolkit:
   • In the “TOOLKITS” section of the agent configuration, click the “+Toolkit” icon
   • Select your desired Azure DevOps toolkit (Wiki, Boards, or Test Plans) from the dropdown menu
   • The toolkit will be added to your agent with the previously configured tools enabled

​

In Pipelines:

1. Navigate to Pipelines: Open the sidebar and select Pipelines.
2. Create or Edit Pipeline: Either create a new pipeline or select an existing pipeline to edit.
3. Add Azure DevOps Toolkit:
   • In the “TOOLKITS” section of the pipeline configuration, click the “+Toolkit” icon
   • Select your desired Azure DevOps toolkit from the dropdown menu
   • The toolkit will be added to your pipeline with the previously configured tools enabled

​

In Chat:

1. Navigate to Chat: Open the sidebar and select Chat.
2. Start New Conversation: Click +Create or open an existing conversation.
3. Add Toolkit to Conversation:
   • In the chat Participants section, look for the Toolkits element
   • Click to add a toolkit and select your desired Azure DevOps toolkit from the available options
   • The toolkit will be added to your conversation with all previously configured tools enabled
4. Use Toolkit in Chat: You can now directly interact with Azure DevOps by asking questions or requesting actions that will trigger the toolkit tools.

​

Instructions and Prompts for Using the Azure DevOps Toolkits

• Direct and Action-Oriented: Employ strong action verbs and clear commands to initiate actions. For example, “Use the ‘get_wiki_page_by_path’ tool…”, “Create a work item using ‘create_work_item’…”, “List all open pull requests…”.
• Parameter-Centric: Clearly enumerate each parameter required by the tool. For each parameter, specify:
  • Its name (exactly as expected by the tool)
  • How the Agent should obtain the value – whether from user input, derived from previous steps in the conversation, retrieved from an external source, or a predefined static value
• Contextually Rich: Provide sufficient context so the Agent understands the overarching objective and the specific scenario in which each Azure DevOps tool should be applied within the broader workflow. Explain the desired outcome or goal for each tool invocation.
• Step-by-Step Structure: Organize instructions into a numbered or bulleted list of steps for complex workflows. This helps the Agent follow a logical sequence of actions.
• Add Conversation Starters: Include example conversation starters that users can use to trigger this functionality. For example, “Conversation Starters: ‘Show me the release notes’, ‘Create a bug report’, ‘List all test plans’”

1. State the Goal: Begin by clearly stating the objective you want to achieve with this step. For example, “Goal: To retrieve the content of a specific wiki page in Azure DevOps.”
2. Specify the Tool: Clearly indicate the specific Azure DevOps tool to be used for this step. For example, “Tool: Use the ‘get_wiki_page_by_path’ tool.”
3. Define Parameters: Provide a detailed list of all parameters required by the selected tool. For each parameter:
   • Parameter Name: <Parameter Name as defined in tool documentation>
   • Value or Source: <Specify the value or how to obtain the value. Examples: "user input", "from previous step", "hardcoded value 'main'", "value of variable X">
4. Describe Expected Outcome (Optional but Recommended): Briefly describe the expected result or outcome after the tool is successfully executed. For example, “Outcome: The Agent will display the wiki page content to the user.”
5. Add Conversation Starters: Include example conversation starters that users can use to trigger this functionality. For example, “Conversation Starters: ‘Show me the release notes’, ‘What are the latest updates?’, ‘Display the project wiki’”

1. Goal: Retrieve content from a specific wiki page in Azure DevOps Wiki.
2. Tool: Use the "get_wiki_page_by_path" tool.
3. Parameters:
    - wiki_path: "Get the wiki page path from the user. Example: '/Release Notes/Latest'"
    - wiki_identifier: "Use the default wiki or ask the user which wiki to access"
4. Outcome: The agent will display the wiki page content to the user with proper formatting.

1. Goal: Create a new work item in Azure Boards based on user requirements.
2. Tool: Use the "create_work_item" tool.
3. Parameters:
    - work_item_type: "Ask the user for the work item type (Task, Bug, User Story, etc.)"
    - title: "Get the work item title from the user"
    - description: "Ask the user for work item details"
    - assigned_to: "Optional - ask if the work item should be assigned to someone"
4. Outcome: A new work item will be created in Azure Boards. Confirm the creation to the user with the work item ID.

​

Chat Usage Examples by Tool Category

User: "Show me the latest release notes from our project wiki."

Agent Response: [Agent uses get_wiki_page_by_path tool]

📄 **Release Notes - Version 2.5.0**

**Released**: November 10, 2025

**New Features**:
- Enhanced user authentication with OAuth 2.0 support
- Real-time collaboration features in document editing
- Advanced search capabilities with AI-powered suggestions

**Bug Fixes**:
- Fixed issue with file upload timeouts
- Resolved memory leak in background processes
- Corrected timezone display in activity logs

**Known Issues**:
- Mobile app may experience slow loading on 3G connections
- Some users report intermittent sync delays

For detailed technical documentation, please refer to the Technical Release Notes section.

User: "Add today's meeting notes to the 'Team Meetings' wiki page."

Agent Response: [Agent uses modify_wiki_page tool]

✅ **Wiki Page Updated Successfully!**

- **Page**: Team Meetings
- **Path**: /Project Documentation/Team Meetings
- **Updated**: November 12, 2025

**Added Content**:
```markdown
## Meeting - November 12, 2025

**Attendees**: John, Sarah, Mike, Lisa
**Duration**: 1 hour

**Agenda**:
1. Sprint review and retrospective
2. Planning for next release
3. Technical debt discussion

**Key Decisions**:
- Approved migration to new testing framework
- Set release date for Version 2.6.0 to December 1st
- Allocated resources for performance optimization

**Action Items**:
- John: Update API documentation by Nov 15
- Sarah: Review security audit findings
- Mike: Prepare deployment checklist

The meeting notes have been successfully added to the Team Meetings wiki page.

User: "Find all high-priority bugs assigned to me."
User: "Find all high-priority bugs assigned to me."

Agent Response: [Agent uses search_work_items tool]

🔍 **Search Results: High-Priority Bugs** (3 items):

1. **Bug #1234**: Application crashes on file upload
   - **Priority**: High (Priority 1)
   - **State**: Active
   - **Assigned To**: You
   - **Created**: Nov 8, 2025

2. **Bug #1245**: Memory leak in background service
   - **Priority**: High (Priority 1)
   - **State**: Active
   - **Assigned To**: You
   - **Created**: Nov 10, 2025

3. **Bug #1251**: Data validation error in user registration
   - **Priority**: High (Priority 1)
   - **State**: Active
   - **Assigned To**: You
   - **Created**: Nov 11, 2025

These high-priority bugs require immediate attention. Would you like details on any specific bug?

User: "Create a new task to update the API documentation."

Agent Response: [Agent uses create_work_item tool]

✅ **Work Item Created Successfully!**

- **Work Item ID**: #1256
- **Type**: Task
- **Title**: Update API documentation
- **State**: New
- **Priority**: Medium (Priority 2)
- **Assigned To**: Unassigned

**Description**:
Update the REST API documentation to reflect recent changes in authentication endpoints and add examples for new OAuth 2.0 flows.

**Created**: November 12, 2025

The task has been added to your Azure Boards backlog and is ready for assignment and planning.

User: "Change the status of work item #1234 to 'In Progress'."

Agent Response: [Agent uses update_work_item tool]

✅ **Work Item Updated Successfully!**

- **Work Item ID**: #1234
- **Title**: Application crashes on file upload
- **Updated Field**: State
- **New Value**: In Progress
- **Previous Value**: Active

The work item status has been updated. The team will be notified of this progress update.

User: "Create a new test plan for the upcoming 2.6.0 release."

Agent Response: [Agent uses create_test_plan tool]

✅ **Test Plan Created Successfully!**

- **Test Plan ID**: #45
- **Name**: Regression Tests - Release 2.6.0
- **State**: Active
- **Start Date**: November 12, 2025
- **End Date**: November 30, 2025

**Details**:
- **Area Path**: ProjectAlpha/Release 2.6.0
- **Iteration**: Sprint 15
- **Description**: Comprehensive regression testing for Version 2.6.0 including new authentication features and bug fixes

The test plan is now ready for test suite and test case creation. Next steps:
1. Create test suites for different functional areas
2. Add or link test cases to the suites
3. Assign testers and begin test execution

Would you like me to create test suites for this plan?

User: "Show me all test cases in test suite #12."

Agent Response: [Agent uses get_test_cases tool]

📋 **Test Cases in Suite #12: Authentication Tests** (8 cases):

1. **TC-101**: Verify login with valid credentials
   - **Priority**: High
   - **State**: Ready

2. **TC-102**: Verify login with invalid password
   - **Priority**: High
   - **State**: Ready

3. **TC-103**: Verify OAuth 2.0 login flow
   - **Priority**: High
   - **State**: Design

4. **TC-104**: Verify session timeout handling
   - **Priority**: Medium
   - **State**: Ready

5. **TC-105**: Verify multi-factor authentication
   - **Priority**: High
   - **State**: Ready

6. **TC-106**: Verify password reset functionality
   - **Priority**: Medium
   - **State**: Ready

7. **TC-107**: Verify account lockout after failed attempts
   - **Priority**: High
   - **State**: Ready

8. **TC-108**: Verify SSO integration
   - **Priority**: Medium
   - **State**: Design

**Summary**: 6 test cases ready for execution, 2 in design phase. All high-priority cases are ready.

​

Best Practices and Use Cases

​

Troubleshooting

​

Support Contact

​

## FAQ