-
Suggestion
-
Resolution: Won't Do
-
None
-
2
-
2
-
NOTE: This suggestion is for Confluence Data Center. Using Confluence Cloud? See the corresponding suggestion.
Hi everyone,
This is Charlie from the Confluence team. Thank you for your interest in this suggestion.
After reviewing this suggestion we have decided that we are unlikely to prioritise it for the foreseeable future. This change would only benefit instances that were created before Crowd was embedded in Confluence several years ago, and may not provide significant value for those customers. Therefore, we are closing this ticket to align with our current priorities and communicate them to our customers.
You can read more about how we prioritise what to implement here.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center
Description
Earlier versions of Confluence, (pre-Embedded Crowd), used a number of tables such as OS_USER and OS_GROUP that are no longer used by the application and this causes confusion for customers. This feature request is to ask that those tables are removed in a future release to ease customer confusion.
- relates to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-28908] Remove unused database tables
Peter Binney
added a comment - I also believe that the following are no longer used.
external_entities external_members groups local_members users
I say that because we upgraded from 2.8 to 4.3 and find these tables have:
- not been changed since the upgrade
- out of date values
Peter Binney
added a comment - I also believe that the following are no longer used.
external_entities
external_members
groups
local_members
users
I say that because we upgraded from 2.8 to 4.3 and find these tables have:
not been changed since the upgrade
out of date values
Hi everyone,
This is Charlie from the Confluence team. Thank you for your interest in this suggestion.
After reviewing this suggestion we have decided that we are unlikely to prioritise it for the foreseeable future. This change would only benefit instances that were created before Crowd was embedded in Confluence several years ago, and may not provide significant value for those customers. Therefore, we are closing this ticket to align with our current priorities and communicate them to our customers.
You can read more about how we prioritise what to implement here.
To learn more about our recent investments in Confluence Data Center, please check our public roadmap and our dashboards containing recently resolved issues, and current work and future plans.
Kind regards,
Confluence Data Center