38
Reviewed publisher/operator records
scoped publisher/operator records
← All company lists
Service management · October 2026 research
Atlassian Jira publisher and workflow research
Review 38 scoped publisher or operator records with Jira declarations, firsthand workflow accounts or tracker instructions. Twenty concern support software; the remaining 18 cover other recorded scopes. These are publisher-level records, with independent buying groups, current runtime, paid status and whole-organization adoption unverified.
Research dated 2026-10-25. Original source dates and website scope stay with the records.
Atlassian Jira research summary
38 scoped publisher/operator records
Research dated
Contact-free research examples · CSV
Review 38 scoped publisher or operator records with Jira declarations, firsthand workflow accounts or tracker instructions. Twenty concern support software; the remaining 18 cover other recorded scopes. These are publisher-level records, with independent buying groups, current runtime, paid status and whole-organization adoption unverified.
Download the 2-row CSV preview38 scoped publisher/operator records; independent buying groups unverified
20
Support-software scope
publisher/operator records
18
Other recorded Jira scopes
publisher/operator records
Source checks record when a declaration was read; they do not establish when the technology operated.
Preview the list
Research summary and contact-free examples only. Full-file commercial delivery and source reproduction rights remain unresolved.
CSV columns: name · domain · sourceClass · checkedOn · scope
2 companies in the preview
These approved examples illustrate the 2026-10-25 research. They are not a representative sample of all customers.
SonarSource
sonarsource.com
Company support-processor declaration · 2026-10-25
The company designates Jira Service Management for support ticketing. The policy update is dated 5 February 2026; original publication, current runtime and whole-company deployment are unknown.
Hightouch
hightouch.com
Historical company workflow article · 2026-10-25
A company article published on 4 October 2022 describes mirroring product requests between Salesforce and Jira for its teams. The statement supports that dated workflow; continued use is unknown.
Research findings
WhosBuilt analysis of the saved October 2026 research. Findings describe this selected cohort, not market share.
20 of 38
Support and other workflows
Twenty of the 38 records concern support, troubleshooting or request ticketing. The list therefore needs workflow scope before it can support research about engineering project management.
Payment, current runtime, whole-organization coverage and purchasing authority remain unknown.
Research 2026-10-25 · publisher/operator records · WhosBuilt saved-record analysis
How this list was checked
Source checks span 2026-10-24–2026-10-25. Retained observations and examples keep their original dates.
Review 38 scoped publisher or operator records with Jira declarations, firsthand workflow accounts or tracker instructions. Twenty concern support software; the remaining 18 cover other recorded scopes. These are publisher-level records, with independent buying groups, current runtime, paid status and whole-organization adoption unverified.
| Source class | Count | Scope |
|---|---|---|
| Company support-processor declaration | Not separately counted | 38 scoped publisher/operator records; independent buying groups unverified |
| Historical company workflow article | Not separately counted | 38 scoped publisher/operator records; independent buying groups unverified |
Support and other workflows: 38 scoped publisher/operator records; independent buying groups unverified Source checks record when a declaration was read; they do not establish when the technology operated.
- Source checks record when a declaration was read; they do not establish when the technology operated.
- Payment, current runtime, whole-organization coverage and purchasing authority remain unknown.
- Selected public-source searches favor indexed and detailed disclosures. The counts do not estimate market share or the full customer population.
- Unknown source reuse rights remain separate from a proposal to publish original aggregate facts and minimal paraphrases. Full-file commercial reuse remains unresolved.
- The records preserve checks on 24–25 October 2026. A source update or page check does not establish when a Jira workflow began or whether it continues.
- A processor designation can permit processing without proving active use. A tracker instruction covers the documented product or project only.
- Different projects, modules, sources and namespaces do not add publishers. Publisher deduplication does not prove procurement independence.
- Customer app functionality, connector capability and shared tenant hosts are excluded as supplier own-use proof.
Source access dates do not refresh historical statements. Static signals do not prove execution, payment or buying intent. Published contacts do not establish deliverability or outreach permission.