Trying to unit test web parts results in an error 'Cannot find module "@ms/sp-telemetry"'. This can be due to using SharePoint dependencies e.g. 'SPHttpClient' when creating the React component. This totally blocks being able to unit test web parts, please fix this.

'@microsoft/sp-build-web' Seems to have been updated to remove the previously included testing modules, these do not have to be added back in, to resolve this issue, as we are able to find the most suitable testing modules to replace these.

This issue has been reported by other users:
https://github.com/SharePoint/sp-dev-docs/issues/526
https://github.com/SharePoint/sp-dev-docs/issues/1076
https://github.com/SharePoint/sp-dev-docs/issues/243

There is a verb to activate feature. Sometimes we require to deactivate features which are not required while creating sites. Can there be a separate verb for deactivating features? Also activateFeature but it works only at web level features. Can we have it extended to activate at site collection level?

List items that have an Audience field attached should be audience filtered when retrieved via the REST API.

For example, a list that has link items with the Audience field attached to target particular items at particular groups of people. If the REST APIs are used to retrieve items from this list, then the identity of the requesting user should be optionally used to filter the results based on audience.

The sequence parameter (int) in the custom action schema should allow us to sort the action within the whole menu.

Actually it's only used to sort SPFx actions among themselves.

Related issue : https://github.com/SharePoint/sp-dev-docs/issues/4121

Allow REST clients to update list items a la SystemUpdate. That is, REST clients should be able to update list item metadata without creating a new version and without affecting system columns like authors and timestamps. The same idea for CSOM was recently implemented and I'm puzzled why the REST API is always left behind.
The CSOM idea:
https://sharepoint.uservoice.com/forums/329220-sharepoint-dev-platform/suggestions/15147093-enable-listitem-systemupdate-via-csom

Currently, when we deploy the SPFx ListView Command Set extension solution, each command becomes a separate button. How can I group them under one group like the default new icon, which we have in the list? Please give a provision for the same.

Provide a way to get data about all components that present on page in ApplicationCustomizer like SearchBox, Search, Documents Library, Lists, Navigation bar etc.

The idea is to have full control on user interaction with components.

In example I want to make an additional action when user clicks on folder, file, list item, navigation item, search result item etc...

Ideally to have access to domElement and data model of component.

I want to truncate the string which crosses the width and add '...' at the end. Currently I am able to do that except for adding the '...'. It can be done if the column formatter supports 'text-overflow: ellipsis'.

Today, application extensions in SPFx (command sets, application customizers & field customizers) can't be tested within either the local or SharePoint Online hosted workbench. This is a bummer and a big step backwards to such a cool aspect to the development story with SPFx.

I get that you need a list to work with, but at a minimum, the workbench could have a static list with static data and no other functionality for us to test the customizations on.

My wish is that Microsoft adds support to the workbench for extensions before GA.

Right now there is no API to check that. If you add a security group into a SharePoint group, there is no way to check if the current user is a part of the SharePoint group: The user is not listed in the group.Users and the SharePoint group is not listed in the user.Groups. The 3 APIs that allowed to do this in full trust code are missing from CSOM so we need an alternative.

Remote event receivers can currently, in SharePoint Online, not be added to content types (https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.contenttype_members.aspx). This makes it somehow tedious to catch events that are fired from items of a specific content type is added/updated/deleted. Having the possibility to add an event receiver to a content type would make this scenario easier to implement.

When creating Site Collections through CSOM and providing an LCID. (For example 2067) an exception is thrown.

[Quote]
SiteCreationProperties.Template\r\nParameter name: Specified value is not supported for the SiteCreationProperties.Template parameter." is thrown at ExecuteQuery();
[/Quote]

The Exception is also not pointing in the right direction.
1) It should be possible to create Site Collections providing the LCID
2) When an Invalid Lcid is passed, the exception should point in the right direction.

Simply hide the page canvas until all SpFx WebPart promises have resolved for modern sites

This would conceivably
1. Improve page load performance by not forcing the browser to display several loading gifs/fading animations at the same time
2. Improve user experience by displaying a complete page to the user rather than the page "jumping" constantly during the first 3-10 seconds of loading
3. Allow developers to add minor CSS updates to the page prior to render using the SharePoint Framework without noticeable "jumping"

It is currently not possible to set the Owner of a SharePoint Group using REST API or maybe I don't have right syntax...

Some list/library settings are available via CSOM. Others are available via the list property bag (although that approach is not desirable). However, there are even other advanced settings that don't appear to be accessible (read or write) via CSOM/REST. In particular, the advanced settings for "open documents in the browser" (open in the client application, etc.) or allow "quick edit" (yes/now).

I'm looking at SharePoint 2013 when trying to do this, but I suspect the same problem occurs for SharePoint Online and SharePoint 2016.

Once the Sharepoint Space has been rolled out among all tenants, it would be nice to have a wider and especially accessible 3D data format range.

Regarding Architectural, Engineering, and Construction objects, there is a global open standard based on 3D smart objects called IFC (Industry Foundation Classes), developed by buildingSMART International (+ info https://www.buildingsmart.org/standards/bsi-standards/industry-foundation-classes/ )

It would be a consistent approach from Microsoft to implement this 3D format in Sharepoint Spaces since is a global and open Standard.
https://support.microsoft.com/en-us/office/add-a-3d-object-to-a-sharepoint-space-6e17e4d4-cad1-459d-90ce-01540697214b

When creating sites using a site design (recipe), one of the available verbs is calling an HTTP-triggered Flow to perform some additional configuration on the newly created site.

When installing SPFx solutions in a site, we should similarly be able to specify an HTTP-triggered Flow to be called as a part of the installation process. This would not only allow developers to provision configuration beyond what's currently supported with Feature XML, but also create a consistent development experience across the different workloads (site designs vs. SPFx).

We need the ability to unlock files via CSOM (with an App Only token) via the SPFile.ReleaseLock method. The flow would be similar to what we can accomplish on-prem:

$web = Get-SPWeb http://webUrl
$list = $web.Lists['Documents']
$item = $list.Items[0]
$lockId = $item.File.LockId
$item.File.ReleaseLock($lockId)

This prevents needing to open support cases for long-lived lock files in scenarios where the end user is having connectivity issues causing long exclusive locks to be created, potentially locking the end user out of their own file.