Convert JIRA to Properties

Why Convert JIRA to Properties?

Converting Jira markup to Properties format extracts structured key-value data from Jira issue content. This is useful when Jira contains configuration specifications, environment settings, or localization strings that need to be transformed into application configuration files.

Properties files are the standard configuration format for Java applications, Spring Boot services, and many other JVM-based systems. By converting Jira-documented settings into Properties format, developers can directly use the output in their applications.

This conversion is particularly valuable when Jira issues contain documented configuration parameters, deployment settings, or internationalization strings that need to be extracted and formatted as key-value pairs for use in Java or Spring projects.

Key Benefits of Converting JIRA to Properties:

• Configuration Extraction: Extract settings documented in Jira into usable config files
• Java Integration: Output directly usable by java.util.Properties
• Spring Boot: Create application.properties from Jira-documented configuration
• i18n Support: Extract localization strings into message bundles
• Simple Format: Clean key=value pairs easy to read and edit
• Comment Preservation: Jira headings become section comments
• Dotted Keys: Hierarchical content mapped to dotted key notation

Practical Examples

Example 1: Configuration Spec to Properties

Input JIRA file (config.jira):

h1. Application Configuration

h2. Database Settings
||Property||Value||
|Host|localhost|
|Port|5432|
|Database Name|myapp_db|
|Max Connections|20|

h2. Server Settings
||Property||Value||
|Server Port|8080|
|Context Path|/api|
|Session Timeout|3600|

Output Properties file (config.properties):

# Application Configuration

# Database Settings
database.host=localhost
database.port=5432
database.name=myapp_db
database.max.connections=20

# Server Settings
server.port=8080
server.context.path=/api
server.session.timeout=3600

Example 2: Localization Strings to Properties

Input JIRA file (messages.jira):

h2. UI Messages

h3. Login Page
* Welcome message: "Welcome to MyApp"
* Username label: "Email Address"
* Password label: "Password"
* Login button: "Sign In"

h3. Error Messages
* Invalid credentials: "Invalid email or password"
* Account locked: "Your account has been locked"
* Session expired: "Your session has expired"

Output Properties file (messages.properties):

# UI Messages

# Login Page
login.welcome.message=Welcome to MyApp
login.username.label=Email Address
login.password.label=Password
login.button=Sign In

# Error Messages
error.invalid.credentials=Invalid email or password
error.account.locked=Your account has been locked
error.session.expired=Your session has expired

Example 3: Deployment Settings to Properties

Input JIRA file (deploy.jira):

h2. Production Environment

||Setting||Value||
|API URL|https://api.production.example.com|
|CDN URL|https://cdn.example.com|
|Log Level|WARN|
|Cache TTL|3600|

{panel:title=Security}
* Enable HTTPS: *true*
* CORS Origins: https://app.example.com
* Rate Limit: 1000 req/min
{panel}

Output Properties file (deploy.properties):

# Production Environment
api.url=https://api.production.example.com
cdn.url=https://cdn.example.com
log.level=WARN
cache.ttl=3600

# Security
security.https.enabled=true
security.cors.origins=https://app.example.com
security.rate.limit=1000

Frequently Asked Questions (FAQ)

Q: How are Jira tables converted to Properties?

A: Jira tables with key-value columns (||Property||Value||) are converted to key=value pairs in the Properties file. The table headers and section headings help determine the dotted key prefix for hierarchical organization.

Q: Are Jira headings preserved in the Properties file?

A: Yes. Jira headings are converted to comment lines (# heading text) in the Properties file, providing section organization and documentation within the configuration file.

Q: Can I use the Properties file with Spring Boot?

A: Yes. The output follows standard Properties file conventions compatible with Spring Boot's application.properties. You can use the file directly or merge its content into your existing configuration.

Q: How are special characters handled?

A: Special characters in values are properly escaped according to Properties file conventions. Characters like backslash, equals sign, and colon in values are escaped with a preceding backslash.

Q: Are dotted keys used for hierarchical content?

A: Yes. Content nested under headings is mapped to dotted key notation. For example, content under "Database Settings" might produce keys like database.host, database.port, providing a logical hierarchy.

Q: Can I use the output for Java internationalization?

A: Yes. Properties files are the standard format for Java i18n message bundles (ResourceBundle). If your Jira content contains UI strings, the converted Properties file can serve as a message bundle.

Q: How is non-tabular Jira content handled?

A: Non-tabular content such as lists and paragraphs are converted to Properties entries where headings become keys and the content becomes values. Code blocks and quotes are preserved as multi-line values where appropriate.

Q: What encoding does the Properties file use?

A: The output defaults to UTF-8 encoding. Traditional Java Properties files use ISO-8859-1, but modern Java applications (Java 9+) support UTF-8 Properties files natively.