Change log level to info for inaccessible Jira issue links

[kkaarreell]

This makes permission or non-existence issues more visible when attempting to link Jira issues, as they were previously only logged at debug level.

🤖 Generated with Claude Code

Summary by Sourcery

Enhancements:

• Log inaccessible or non-existent Jira issue links at info level instead of debug to improve observability.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Raises the log level from debug to info when Jira issue link creation fails because the target issue does not exist or is inaccessible, making these failures more visible in logs.

Sequence diagram for Jira issue link failure logging at info level

sequenceDiagram
    participant JiraService
    participant JiraAPI
    participant Logger

    JiraService->>JiraAPI: add_issue_links(linked_key)
    JiraAPI-->>JiraService: JIRAError
    alt logger_present
        JiraService->>Logger: info(Target issue does not exist or is not accessible)
    else no_logger
        JiraService-->>JiraService: skip_logging
    end
    JiraService-->>JiraService: continue_with_next_link

Loading

File-Level Changes

Change	Details	Files
Increase logging severity for inaccessible or non-existent Jira issues during link creation.	Change logger call for Jira link failure from debug to info within the add_issue_links flow Maintain existing error handling behavior (catch, log, continue) while only adjusting log visibility	newa/services/jira_service.py

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've left some high level feedback:

• Consider logging the exception details (e.g., status code or error message) alongside the Jira key to make the INFO log more actionable for diagnosing why the issue is inaccessible.
• If this path can be hit frequently in normal operation, it may be worth evaluating whether INFO is the right level here to avoid excessive log noise in high-volume environments.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider logging the exception details (e.g., status code or error message) alongside the Jira key to make the INFO log more actionable for diagnosing why the issue is inaccessible.
- If this path can be hit frequently in normal operation, it may be worth evaluating whether INFO is the right level here to avoid excessive log noise in high-volume environments.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}