You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added Jira Cloud compatibility — the module now auto-detects Cloud vs Data Center/Server via Get-JiraServerInformation and adapts API calls accordingly
Added ConvertFrom-AtlassianDocumentFormat public function (alias ConvertFrom-ADF) — converts ADF objects (Jira Cloud v3) to Markdown; plain strings (Data Center) are passed through unchanged
Added ConvertTo-AtlassianDocumentFormat public function (alias ConvertTo-ADF) — converts Markdown to ADF for writing descriptions and comments on Jira Cloud v3
Added -AccountId parameter to Get-JiraUser for Cloud's account-based user lookup
Added -Force parameter to Get-JiraServerInformation to bypass the server info cache
Added Jira Cloud vs Data Center compatibility guidance in documentation
Changed
User operations now use accountId on Cloud, username/name on Data Center (Get-JiraUser, Set-JiraUser, Remove-JiraUser, New-JiraIssue, Set-JiraIssue, Invoke-JiraIssueTransition, Add-JiraGroupMember, Remove-JiraGroupMember, Add-JiraIssueWatcher, Remove-JiraIssueWatcher, Resolve-JiraUser)
Get-JiraIssue JQL search uses /rest/api/3/search/jql with token-based pagination on Cloud
Get-JiraServerInformation now caches its result in module scope; subsequent calls return cached data (cleared on Set-JiraConfigServer or with -Force)
ConvertTo-JiraComment and ConvertTo-JiraIssue now convert ADF responses to readable Markdown text
ConvertTo-JiraUser.ToString() falls back to DisplayName or AccountId when Name is empty (GDPR compliance)
Get-JiraIssueWatcher now pipes watchers through ConvertTo-JiraUser for consistent typed output
Modernized test infrastructure and standardized helper utilities (#549)