You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I was revisiting several of the issues & bugs that I have reported (and were turned into
https://jira.atlassian.com/... issues. And I am seeing VERY few that hve recent responses by Atlassian people.
Examples:
https://jira.atlassian.com/browse/CONFCLOUD-66771 -- Created 2019-06-04, 0 comments by Atlassian staff --- "Reporter" Vinicius Siqueira "Assignee" Klaus Ihlberg
https://jira.atlassian.com/browse/CONFCLOUD-66613 -- Created 2019-05-20, 0 comments by Atlassian staff --- "Reporter" Shakiru Ayanloye "Assignee" Klaus Ihlberg
I just scanned several other pages, and while Atlassian staff create and update the pages, they very rarely seem to comment on the pages.
@Jessica Taylor , @Sunny Xu @Traci Wilbanks --- Any response?
Hello Bob,
Thank you for bringing those bug tickets to my attention. I've closed the 2nd one as a duplicate and linked the two together, so we can focus our efforts on CONFCLOUD-66771.
To answer your question, jira.atlassian.com is the primary place where bugs and feature requests should be logged. The activity there is what helps us to prioritize our bug fixing and feature implementation. For more details, have a look at Atlassian Cloud Bug Fix Policy (a Server version is also available.) We also have a separate procedure for implementing New Features but this also relies on jira.atlassian.com.
Many of the replies you may not see from other Atlassians because they contain sensitive customer details for the purpose of replicating and are being restricted for that reason. Another reason is that the development teams may also have their own internal queues, so while it may not appear that way, they are working on the cases behind the scenes. Important updates will be included on the public facing bug when there are details available.
Community is also a great way to keep in touch with us and provide feedback. For example, our Confluence product manager has been active in Q&A sessions and you can find a few of his threads below:
You're also welcome to schedule some time with Avi if you would like to raise some of the recent pain points that you've been experiencing with the new editor in Confluence.
I hope that helps, but let me know if you have any questions about this.
Regards,
Shannon
Thank you for updating this Shannon!
Hi Bob, I've also made an update on https://jira.atlassian.com/browse/CONFCLOUD-66771 as it looks like we had put this in our long-term backlog.
Best,
Sunny
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As I see most of issues are commented.
I hope the prio related to your request.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess that we are done communicating directly with Pratima Arora anymore. While I can still find @user1603166931620 for several Atlassian employees, Pratima is no longer reachable.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.