Have you ever struggled to organize team events or gather company-wide opinions in Confluence? If so, you're likely familiar with Multivote & Enterprise Survey for Confluence, one of our flagship apps that is designed to simplify the voting process.
We are TNG Technology Consulting GmbH - a values-based consulting company focused on solving hard IT problems. As a long-time Atlassian Solution Partner, we have developed a range of solutions to optimize the processes of our customers and our own processes. Our journey as an Atlassian Marketplace vendor began with open-source plugins, which eventually evolved into a dedicated product team.
Today, we're excited to share the story behind our latest feature release for Multivote & Enterprise Survey for Confluence, designed to significantly improve the user experience for Survey managers.
Multivote & Enterprise Survey provides a Survey macro, which you can put on a Confluence page and create a Survey dynamically while you are viewing the page. If you frequently organize events, it can be easy to lose track of the Survey macros you've created and their locations. With our brand new Manage Surveys feature, you can effortlessly interact with and manage your Surveys without worrying about how to find them in your Confluence tree.
This feature provides a centralized overview of all your managed Surveys, allowing you to:
View key information about the Surveys such mode, anonymity or most recent response time, and navigate to Confluence pages containing your Surveys via linked pages
This new feature is available in both Cloud and Data Center version of Multivote & Enterprise Survey. For more detailed information on how to use the Manage Surveys feature, please see our Cloud documentation and our Data Center documentation.
If you are already using Multivote & Enterprise Survey in your Confluence instance, then update your app to the latest version to check these new functionalities out. If you have never tried out Multivote & Enterprise Survey, it is available for both Confluence DC and Confluence Cloud. Start your free trial on the Atlassian Marketplace and check it out. If you have any feedback or questions, you can always reach us via e-mail at atlassian-apps@tngtech.com
What do you do if you are done with a Survey and you do not want it lying around. The easy answer is, delete the Survey macro from your page, or directly delete the page itself. Unfortunately, there are a few shortcomings of this approach, mainly because our Surveys are designed to be independent from the Confluence pages where their associated macros are placed. First, you can end up with orphaned Surveys that are no longer easily accessible if all associated macros and pages are deleted. Second, if you really want to get rid of the data, e.g. for maintaining your GDPR compliance, deleting the macro would not be enough as the Survey data would still be somewhere in your Confluence database.
The Delete Survey feature in the Manage Surveys page does not only provide you with an easy way of detecting and removing your orphaned Survey macros, but also makes sure that all data associated to the deleted Survey is purged from your Confluence database.
If you delete the Survey from Manage Surveys page without deleting the Survey macro from the Confluence page that it belongs, then the Survey macro will be replaced with a placeholder that indicates that the Survey data is deleted.
As it was already mentioned, it is possible to end up with an orphaned Survey, e.g. when all macros associated to this Survey have been deleted. If this Survey has some managers, they can manage and delete it via their Manage Surveys page. However, in the case where there are no managers of this Survey available anymore, e.g. left the company, we want to provide a way to manage this Survey.
As an admin, you can directly interact with the data of a Survey by accessing the Cloud storage or Data Center database. To make this process more straightforward for admins we introduce an administrator version of the Manage Surveys feature here they can access all Surveys on the instance.
This feature uses a separate backend endpoint only available to administrators which fetches all Surveys. We want ensure accountability in accordance to how Atlassian handles administrators escalating their privileges to access restricted content. We achieve this by hiding this feature behind a toggle, and writing to the audit log whenever this admin only endpoint was accessed.
Tim Zemlin [TNG]
TNG Technology Consulting GmbH
1 accepted answer
0 comments