update docs

[hussam789]

PR Type

Documentation

---

Description

• Updated the documentation to provide clearer instructions for Jira integration, including a direct link to the relevant section.
• Clarified the instructions for adding Personal Access Tokens in configuration files.
• Improved the readability of the core abilities list by adding a new line.

---

Changes walkthrough 📝

	Relevant files
Documentation	fetching_ticket_context.md Update Jira integration instructions and configuration details docs/docs/core-abilities/fetching_ticket_context.md Updated link format for Jira integration instructions. Clarified configuration file instructions for adding PAT. +2/-2
Formatting	index.md Improve readability of core abilities list                              docs/docs/core-abilities/index.md Added a new line for better readability. +1/-0

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[codiumai-pr-agent-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🏅 Score: 95

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[codiumai-pr-agent-pro]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Best practice	Use relative links for internal documentation references to improve maintainability Consider using a relative link instead of an absolute URL for internal documentation references. This makes it easier to maintain the documentation and ensures links work correctly in different environments. docs/docs/core-abilities/fetching_ticket_context.md [12] -2. For Jira tickets, you should follow the instructions in [Jira Integration](https://qodo-merge-docs.qodo.ai/core-abilities/fetching_ticket_context/#jira-integration) in order to authenticate with Jira. +2. For Jira tickets, you should follow the instructions in [Jira Integration](#jira-integration) in order to authenticate with Jira. Apply this suggestion Suggestion importance[1-10]: 7 Why: Using relative links for internal documentation is a good practice as it improves maintainability and ensures links work correctly across different environments. This change would make the documentation more robust.	7
Enhancement	Provide more specific guidance on configuration file location to improve clarity Provide more specific guidance on where to add the configuration lines. Mentioning "Configuration file/Environment variables/Secrets file" might be too vague for some users. docs/docs/core-abilities/fetching_ticket_context.md [109] -2. In your Configuration file/Environment variables/Secrets file, add the following lines: +2. Add the following lines to your configuration file (e.g., `config.toml`), environment variables, or secrets file, depending on your setup: Apply this suggestion Suggestion importance[1-10]: 6 Why: The suggestion provides more specific guidance on where to add configuration lines, which can help users better understand where to make changes. This improves clarity and reduces potential confusion.	6

• Author self-review: I have reviewed the PR code suggestions, and addressed the relevant ones.

💡 Need additional feedback ? start a PR chat