We have just uploaded a new version of the JiraPS module to the Gallery and to GitHub.
Description
This release brings Jira Cloud compatibility to JiraPS! The module now auto-detects whether you’re connecting to Jira Cloud or Data Center/Server and adapts API calls accordingly. This includes support for Atlassian Document Format (ADF) conversion and account-based user identification.
Change Log
Added
- Added Jira Cloud compatibility — the module now auto-detects Cloud vs Data Center/Server via
Get-JiraServerInformationand adapts API calls accordingly - Added
ConvertFrom-AtlassianDocumentFormatpublic function (aliasConvertFrom-ADF) — converts ADF objects (Jira Cloud v3) to Markdown - Added
ConvertTo-AtlassianDocumentFormatpublic function (aliasConvertTo-ADF) — converts Markdown to ADF for writing descriptions and comments on Jira Cloud v3 - Added
-AccountIdparameter toGet-JiraUserfor Cloud’s account-based user lookup - Added
-Forceparameter toGet-JiraServerInformationto bypass the server info cache - Added HTTP 429 rate limit handling with automatic retry (respects
Retry-Afterheader, exponential backoff) - Added Jira Cloud vs Data Center compatibility guidance in documentation
Changed
- User operations now use
accountIdon Cloud,username/nameon Data Center Get-JiraIssueJQL search uses/rest/api/3/search/jqlwith token-based pagination on CloudGet-JiraServerInformationnow caches its result in module scopeConvertTo-JiraCommentandConvertTo-JiraIssuenow convert ADF responses to readable Markdown textConvertTo-JiraUser.ToString()falls back toDisplayNameorAccountIdwhenNameis empty (GDPR compliance)- Modernized test infrastructure and standardized helper utilities
Fixed
- Enforced UTF-8 with BOM across all PowerShell files for PS v5 compatibility
- Fixed
inlineCardrendering inConvertFrom-ADF - Fixed table separator regex in
ConvertTo-ADFto handle compact separators without spaces - Fixed typos and casing errors in test assertions and fixtures
Full list of changes can be found in CHANGELOG.