-
Notifications
You must be signed in to change notification settings - Fork 504
Closed
Copy link
Labels
affects: 7.xIssue impacts 7.x releasesIssue impacts 7.x releasesaffects: 8.xIssue impacts 8.x releasesIssue impacts 8.x releasesaffects: 9.xIssue impacts 9.x releasesIssue impacts 9.x releasesaffects: mainIssue impacts "main" (latest release).Issue impacts "main" (latest release).bugcomponent: Discoveryrelated to discovery search or browse systemrelated to discovery search or browse system
Milestone
Description
Describe the bug
When adding a sub-community in 7.6.2 and earlier, if the user was on a community page that community would be at the top of the "Create a new community in" list. As of 7.6.3 this is not the case and the list is just alphabetical.
When adding a collection, the current community is still at the top of the list.
This can also be seen in the 9.1 snapshot on https://demo.dspace.org/
When adding a collection, an additional REST call is made before the community list, to load the current community. This REST call was also made when adding a community in 7.6.2 and earlier.
To Reproduce
Steps to reproduce the behavior:
- Log in as a user with the ability to create communities
- Browse to an existing community
- Click New -> Community from the sidebar
- The "Create a new community in" list does not start with the current community
Expected behavior
The current community should be at the top of the list, as it is when adding a collection.
Related work
Link to any related tickets or PRs here.
Metadata
Metadata
Assignees
Labels
affects: 7.xIssue impacts 7.x releasesIssue impacts 7.x releasesaffects: 8.xIssue impacts 8.x releasesIssue impacts 8.x releasesaffects: 9.xIssue impacts 9.x releasesIssue impacts 9.x releasesaffects: mainIssue impacts "main" (latest release).Issue impacts "main" (latest release).bugcomponent: Discoveryrelated to discovery search or browse systemrelated to discovery search or browse system
Type
Projects
Status
✅ Done