Atlas Suggestions

Atlas Suggestions
We want this to be the best community it can possibly be! So let us know what you think, or how we can help improve your experience on Atlas. Please be sure to follow the Idea submission guidelines.
Hi Khoros Team, The Label API is the Khoros community. We can only able to sort now by using Label id (Label creation time) and text (by alphabetical) order. If we have order sort order like Top Labels( Post with the highest Label) or displaying ... See more...
Hi Khoros Team, The Label API is the Khoros community. We can only able to sort now by using Label id (Label creation time) and text (by alphabetical) order. If we have order sort order like Top Labels( Post with the highest Label) or displaying the label order by most recent activity(New Topic or Edit action performed) will be helpful. Thanks, Abhishek Illindra
Tags (1)
Yesterday I merged https://community.esri.com/t5/python-ideas/create-annotation-feature-class-tool/idi-p/1006570/jump-to/first-unread-message (idea 2) with an existing idea: https://community.esri.com/t5/arcgis-pro-ideas/geoprocessing-toolset-for-c... See more...
Yesterday I merged https://community.esri.com/t5/python-ideas/create-annotation-feature-class-tool/idi-p/1006570/jump-to/first-unread-message (idea 2) with an existing idea: https://community.esri.com/t5/arcgis-pro-ideas/geoprocessing-toolset-for-creating-and-manipulating-annotation/idi-p/938650 (idea 1).  Because a user is not allowed to give their own idea kudos, idea 2 had 0 kudos.  So when it is merged and Merge Kudos is applied, there are 0 kudos added to idea 1.  While this may be technically correct, it is not logically correct.  As long as the poster of idea 2 has not already voted for idea 1, then 1 vote should be added to idea 1.  This is not the case, and it would be great if this logic could be corrected so that the number of kudos on idea 1 reflects real demand. With the way that it works now, you can see that I have to ask the second user (poster of idea 2) to vote for idea 1.  That user experience is less than ideal and it would be great if the Merge Kudos functionality handled the transaction automatically. Thank you!
Tags (2)
This is something very useful and very helpful for every community who wants to put there community to maintenance mode at there own, without any help of developers or to open support ticket. There are few cases where a community need some enhancem... See more...
This is something very useful and very helpful for every community who wants to put there community to maintenance mode at there own, without any help of developers or to open support ticket. There are few cases where a community need some enhancements or update for new release to be go-live, and Admin or Moderators want to confirm the updates on production before it went live for every users. Its becomes a challenge when Admin/moderator is non-technical to write the code and there is no developers to help them for this change. Its just a matter of one small feature which can save a lot of time for every publish. Also once the confirmation is done, they will no need for one more deployment to remove that condition to check for maintenance mode and go-live. I get to know in 20.1 release there is new feature to pause notification emails while performing maintenance work on the community. I think include these fields in same settings page will help to verify at one place for this feature.
0 Kudos
Every time I attempt to update my email address, I save and it says it was successful - but the old email address is still there. My new email address is a gmail account - is that causing the problem? Thanks!
0 Kudos