Struct Jira 

pub struct Jira { /* private fields */ }

Jira API client with session management capabilities.

This client handles authentication, session caching, and issue retrieval from Jira instances. It implements the Session trait for automatic credential management and retry logic.

Thread Safety

The client is not thread-safe due to mutable retry state. Each thread should use its own client instance for concurrent operations.

Session Lifecycle

1. Initialization: Client created with configuration
2. Authentication: Credentials prompted when first needed
3. Session Caching: Successful sessions stored for reuse
4. Automatic Retry: Expired sessions trigger re-authentication
5. Error Handling: Persistent failures return empty results

Implementations

impl Jira

pub fn new(config: &JiraConfig) -> Self

Creates a new Jira API client instance.

Initializes the HTTP client with default settings suitable for Jira API interactions. The client is configured for JSON requests and includes appropriate timeout and connection settings.

Arguments

• config - Configuration containing Jira URL and login information

Examples

use kasl::api::{Jira, JiraConfig};

let config = JiraConfig {
    login: "username".to_string(),
    api_url: "https://jira.company.com".to_string(),
};
let jira = Jira::new(&config);

pub async fn get_completed_issues( &mut self, date: &NaiveDate, ) -> Result<Vec<JiraIssue>>

Retrieves all issues completed by the current user on a specific date.

This method performs a sophisticated issue search using JQL (Jira Query Language) to find issues that were marked as completed on the specified date. The search includes robust error handling and automatic session management with retry logic.

JQL Query Details

The search uses the following criteria:

• Status Filter: Issues with status “Done” or “Решена” (supports localized Jira)
• Resolution Date: Issues resolved within the full day range (00:00 to 23:59)
• Assignee Filter: Only issues assigned to the current user (currentUser())

Session Management

The method implements sophisticated session handling:

1. Session Retrieval: Get or create a valid session token using the Session trait
2. API Request: Execute the JQL search with session cookie authentication
3. Error Handling: Detect HTTP 401 (Unauthorized) responses indicating expired sessions
4. Automatic Retry: Clear cached session and retry authentication up to the limit
5. Graceful Degradation: Return empty results on persistent authentication failures

Error Recovery Strategy

Unlike other API integrations, Jira errors are allowed to propagate rather than returning empty results silently. This is because Jira data is typically more critical for work tracking, and users should be aware of connection issues.

However, authentication failures are handled gracefully with automatic retry logic and eventual fallback to empty results after exhausting retries.

Date Handling

The method formats the provided date to ensure proper JQL syntax and covers the entire day from midnight to 23:59 to capture all possible resolution times within the target date.

Arguments

• date - The date to search for completed issues (in any timezone)

Returns

Returns a vector of JiraIssue objects representing completed work. Returns an empty vector if:

• No issues are found matching the criteria
• Authentication fails persistently after all retries
• Network errors occur during the request

Errors

May return errors for:

• JSON parsing failures in API responses
• Unexpected HTTP response formats
• Session token formatting errors

Network errors and authentication failures are handled gracefully and result in empty results rather than propagated errors.

Examples

let config = JiraConfig {
    login: "username".to_string(),
    api_url: "https://jira.company.com".to_string(),
};
let mut jira = Jira::new(&config);

let today = chrono::Local::now().date_naive();
let issues = jira.get_completed_issues(&today).await?;

for issue in issues {
    println!("Completed: {} - {}", issue.key, issue.fields.summary);
}

Trait Implementations

impl Debug for Jira

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Session for Jira

async fn login(&self) -> Result<String>

Performs session-based authentication with Jira.

This method implements Jira’s session authentication flow using the REST API. It sends user credentials to the authentication endpoint and receives a session cookie that can be used for subsequent requests.

Authentication Process

1. Credential Validation: Ensures credentials are set before proceeding
2. HTTP Request: POST to the session authentication endpoint with JSON credentials
3. Response Validation: Checks for successful HTTP status codes
4. Cookie Extraction: Parses session information from the response
5. Format Preparation: Creates properly formatted cookie string for headers

Session Cookie Format

The returned session ID is formatted as {cookie_name}={cookie_value} and should be included in the Cookie header of subsequent API requests.

Returns

Returns a formatted session cookie string on successful authentication.

Errors

Returns an error if:

• No credentials have been set (programming error)
• HTTP request fails due to network issues
• Credentials are invalid (401 response)
• Jira returns an unexpected response format
• Session parsing fails

fn set_credentials(&mut self, password: &str) -> Result<()>

Sets user credentials for Jira authentication.

Stores the provided username and password in memory for use during the authentication process. This method is called by the session management system when credentials are needed.

Security Notes

• Credentials are only stored in memory temporarily
• Password is stored in plain text for authentication
• No persistence to disk or configuration files
• Credentials are cleared after successful authentication

Arguments

• password - The user’s Jira password in plain text

Returns

Always returns Ok(()) as this operation cannot fail.

fn session_id_file(&self) -> &str

Returns the filename for storing Jira session tokens.

The session file is stored in the user’s application data directory and contains the cached session token for automatic login restoration.

fn secret(&self) -> Secret

Returns a configured Secret instance for secure password prompting.

The Secret manager handles secure password input with hidden characters and optional encrypted caching in the user’s data directory.

Returns

A configured Secret instance with Jira-specific prompts and file names.

fn retry(&self) -> i32

Returns the current authentication retry count.

Used by the session management system to track failed authentication attempts and implement retry limits.

fn inc_retry(&mut self)

Increments the authentication retry counter.

Called after each failed authentication attempt to track progress toward the maximum retry limit defined in the session management system.

fn reset_retry(&mut self)

Resets the authentication retry counter to zero.

Called after successful authentication to ensure future session requests start with a clean slate.

async fn get_session_id(&mut self) -> Result<String>

Retrieves or establishes a valid session ID.

fn read_session_id(file_name: &str) -> Result<String>

Reads a session ID from the specified file.

fn write_session_id(file_name: &str, session_id: &str) -> Result<()>

Writes a session ID to the specified file.

fn delete_session_id(&self) -> Result<()>

Deletes the cached session file.