Struct JiraConfig 

pub struct JiraConfig {
    pub login: String,
    pub api_url: String,
}

Configuration for Jira API integration.

This structure holds the necessary information for connecting to Jira instances, including both cloud and server/data center deployments. The configuration is designed to be serializable for storage in configuration files.

Security Notes

• Passwords are never stored in configuration files
• Only usernames and API endpoints are persisted
• Session tokens are cached separately with encryption
• Configuration files should have restricted permissions

Supported Jira Instances

• Atlassian Cloud: Uses https://company.atlassian.net format
• Server/Data Center: Uses custom domain like https://jira.company.com
• Local Development: Can use http://localhost:8080 for testing

Fields

login: String

Jira username for authentication.

This should be the actual username, not an email address, unless your Jira instance is configured to use email addresses as usernames. Check with your Jira administrator if unsure.

For Atlassian Cloud instances, this is typically the email address used to register the account.

api_url: String

Base URL of the Jira instance.

Examples:

• Atlassian Cloud: https://company.atlassian.net
• Server/Data Center: https://jira.company.com
• Local development: http://localhost:8080

Do not include the /rest/api/ path as it will be added automatically. The URL should point to the root of your Jira installation.

Implementations

impl JiraConfig

pub fn module() -> ConfigModule

Returns the configuration module metadata for Jira.

Used by the configuration system to identify and manage Jira-specific settings during interactive setup. This provides the human-readable name and internal key for the module.

Returns

A ConfigModule with Jira identification information.

pub fn init(config: &Option<Self>) -> Result<Self>

Runs an interactive configuration setup for Jira integration.

Prompts the user for Jira instance URL and username, using existing configuration values as defaults if available. This method provides a user-friendly way to configure Jira integration during initial setup or reconfiguration.

Interactive Prompts

1. Username: Prompts for Jira username (or email for cloud instances)
2. API URL: Prompts for Jira instance URL with validation hints

Both prompts will show existing values as defaults if configuration already exists, making it easy to update only specific values without re-entering everything.

Configuration Validation

While this method doesn’t validate the actual connection to Jira, it provides helpful prompts and examples to guide users toward correct configuration values.

Arguments

• config - Existing Jira configuration to use as defaults (if any)

Returns

• Result<Self> - New Jira configuration with user input

Errors

Returns an error if:

• Terminal input/output fails
• User cancels the configuration process
• Input validation fails

Example

let existing_config = Some(JiraConfig {
    login: "olduser".to_string(),
    api_url: "https://old-jira.com".to_string(),
});

let new_config = JiraConfig::init(&existing_config)?;

Trait Implementations

impl Clone for JiraConfig

fn clone(&self) -> JiraConfig

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for JiraConfig

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

Formats the value using the given formatter.

impl<'de> Deserialize<'de> for JiraConfig

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for JiraConfig

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.