Create Give feedback to Atlassian Help Administration
Executive summary
Atlassian is actively soliciting customer feedback across Cloud and product channels—docs show explicit “Give feedback” prompts and multiple product-change notices that require admin action by December 1, 2025 (audit log toggle) [1] and reiterations across November updates [2]. Public signals from Atlassian’s blogs and changelog show the company emphasizing AI, automation, and responsible-technology refreshes while inviting feedback on features such as Automation agents and the Discovered products screen [3] [4] [5].
1. Why Atlassian is asking for feedback now — product cadence meets policy deadlines
Atlassian’s Cloud change logs and blog posts repeatedly surface user-facing prompts—“Scroll to the bottom of your Insights and select Give feedback” and targeted action notices like “turn the toggle on in your audit log settings before December 1, 2025,” indicating these requests are tied to concrete product changes and policy deadlines rather than vague market-research exercises [1] [2]. That timing suggests Atlassian is both shepherding customers through configuration changes (logs toggle) and actively gathering reaction to UI/process updates (Discovered products screen) to reduce disruption when changes take effect [1] [5].
2. What Atlassian wants feedback about — features, telemetry and AI
Recent Atlassian communications show clear themes: automation and agent-driven features (Customer Feedback Agent, PRD Agent), responsible AI practices, and Cloud UX/process updates. Atlassian’s Automation blog highlights Customer Feedback and PRD agents intended to synthesize and route feedback into workflows [3]. The “responsible technology” refresh was explicitly framed as the product of “months of gathering feedback from teams both inside and outside Atlassian,” indicating the company is both soliciting and using feedback to refine AI controls and guidance [4].
3. What customers are being told to do — concrete admin steps and deadlines
Several Cloud changelogs include concrete, time-bound actions for admins: the need to enable third‑party app Confluence and Jira API request logging before December 1, 2025 to continue receiving those logs [1] [2]. The documentation also calls out deprecations (the External Asset Platform was shut down in December 2024) and product adjustments like Managed Teams behaviour changes—all reminders that feedback requests are embedded alongside admin-impacting operational notices [1] [5].
4. How Atlassian frames its use of feedback — product-led and research-backed storytelling
Atlassian frames feedback as central to product evolution. The company’s thought pieces and reports (State of Teams, responsible AI refresh) explicitly attribute updates to listening exercises and research—“This refresh is the result of months of gathering feedback” and State of Teams/DevEx reporting are used to justify strategy and feature investments such as asynchronous work tooling and developer experience improvements [4] [6] [7]. That narrative supports product-led growth messaging elsewhere in coverage of Atlassian’s approach [8].
5. Where feedback leads — automation, DevOps positioning, and enterprise controls
Atlassian’s announcements show a link between customer input and roadmap priorities: Automation agents, smart PR feedback, and DevOps platform capabilities are all in focus [3] [9]. The company’s inclusion in Forrester’s DevOps Wave and its promotion of AI-enabled PR/CI tooling suggests feedback is informing higher-level positioning around developer workflow automation and enterprise controls [9].
6. Competing perspectives and hidden incentives to consider
Atlassian’s solicitation of feedback and public framing serve both product improvement and commercial narratives: product teams gain user data to refine features, while marketing gains proof points for leadership in AI and DevOps [4] [9]. Independent coverage and analyst notes referenced around Atlassian’s stock and strategy emphasize a mix of “robust revenue growth” and “financial challenges,” indicating corporate incentives to highlight positive customer‑driven innovation even as markets remain cautious [10] [11].
7. Practical guidance for people giving feedback to Atlassian
If you’re an admin or user affected by these changes: follow the explicit doc instructions (enable audit log toggle before Dec 1 if you need third-party API logs) and use the “Give feedback” affordances in Insights and product pages so your input attaches to the UI change it addresses [1] [2]. For deeper product suggestions—particularly about AI agents and automation—refer to Atlassian’s Automation community and webinar invitations where the company is actively soliciting structured input [3].
Limitations and gaps
Available sources detail where Atlassian asks for feedback, specific admin actions and product narratives, but do not provide reporting on how individual feedback submissions are processed, adjudicated, or the precise timeline from submission to product change; available sources do not mention those operational details [1] [3] [4].