docs: document Jira requirements field and Azure DevOps ticket support

- Document jira_requirements_field (instance-specific custom field id for
  acceptance criteria).
- Add Azure DevOps to the supported git platforms for ticket context, now that
  Jira lookup is provider-agnostic.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Author: dellch

docs/docs/core-abilities/fetching_ticket_context.md

@@ -1,6 +1,6 @@
 # Fetching Ticket Context for PRs
 
-`Supported Git Platforms: GitHub, GitLab, Bitbucket`
+`Supported Git Platforms: GitHub, GitLab, Bitbucket, Azure DevOps`
 
 !!! note "Branch-name issue linking: GitHub only (for now)"
     Extracting issue links from the **branch name** (and the optional `branch_issue_regex` setting) is currently implemented for **GitHub only**. Support for GitLab, Bitbucket, and other platforms is planned for a later release. The GitHub flow was the most relevant to implement first; other providers will follow.
@@ -116,10 +116,22 @@ You can create an API token from your Atlassian account:
 
 ```toml
 [jira]
+jira_base_url = "https://<JIRA_ORG>.atlassian.net"
 jira_api_token = "YOUR_API_TOKEN"
 jira_api_email = "YOUR_EMAIL"
 ```
 
+#### Acceptance criteria / requirements (optional)
+
+To include a ticket's acceptance criteria in the analysis, set `jira_requirements_field`
+to the id of the custom field that holds it. The field id is specific to your Jira
+instance (for example `customfield_10127`); leave it empty to skip requirements.
+
+```toml
+[jira]
+jira_requirements_field = "customfield_10127"
+```
+
 ### Jira Data Center/Server
 
 #### Using Basic Authentication for Jira Data Center/Server