SharePoint
Feedback by UserVoice

Tim Wootton

My feedback

  1. 196 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    An error occurred while saving the comment
    Tim Wootton commented  · 

    I totally support this, we are being forced down the Modern path without being given the useful tools (think classic webparts) to allow us to share distributed information from across our sites. We regularly use timelines on a dashboard style Team page which we currently have to create in classic to accommodate the timeline requirements however at the same time we lose the newer functionality.

    If you are going to replace a product (and then tell us it's being phased out (See - MC177122- SharePoint tenant opt-out for modern lists is retiring in 2019) you could at least provide us with the tools we use, need and are familiar with - alternatively give us newer tools that do the same thing

    Tim Wootton supported this idea  · 
  2. 44 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Sites and Collaboration » Web Parts  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Wootton supported this idea  · 
    An error occurred while saving the comment
    Tim Wootton commented  · 

    I totally support this, we are being forced down the Modern path without being given the useful tools (think classic webparts) to allow us to share distributed information from across our sites. We regularly us timelines on a dashboard style Team page which we currently have to create in classic to accommodate the timeline requirements however at the same time we lose the newer functionality.

    If you are going to replace a product (and then tell us it's being phased out (See - MC177122- SharePoint tenant opt-out for modern lists is retiring in 2019) you could at least provide us with the tools we use, need and are familiar with - alternatively give us newer tools that do the same thing.

  3. 334 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    33 comments  ·  Sites and Collaboration » Web Parts  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tim Wootton commented  · 

    Totally agree, i'm so bemused by the way this platform is going, give us back the tools that made Sharepoint a useful tool and stop tooling around with us. I couldn't give a monkeys about adding embed code or quick charts I want my Charts Web Part, The Content editor, The Script editor, you know the useful stuff that made it possible for us to be dynamic and agile in the deployment of solutions. I get the move to a new platform but limiting the modern environment to SPFx is insane.

    Tim Wootton supported this idea  · 
  4. 22 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  SharePoint Administration » Security  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Tim Wootton commented  · 

    Agreed, with all the privacy laws in place and the new ones coming being able to easily identify who has access to what is paramount, i's take this a step further and also allow us to view permissions from a site/site collection level but at a granular level ie showing who has what rights as a member of what group and who was provided permissions directly

    Tim Wootton supported this idea  · 
  5. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  SharePoint Administration » SharePoint Upgrade  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Wootton supported this idea  · 
  6. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Suggestion Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Wootton supported this idea  · 
  7. 2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Suggestion Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Wootton supported this idea  · 
  8. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Suggestion Archive  ·  Flag idea as inappropriate…  ·  Admin →
    Tim Wootton supported this idea  · 
    An error occurred while saving the comment
    Tim Wootton commented  · 

    I raised this lat year when the issue was first noticied and they actually rolled the change back, now i see the poorly formateed notifications are back.. we contacted MS;

    Here is their response:

    Hi Tim

    Sorry for letting you wait for so many days. These days, I have made multiple conversations with the product team who is responsible for the alert mail coding . Together with their manager, they still decide this issue as ‘won’t fix’. I am so sorry about the fact since they have the authority to decide whether to fix this or not, and we can do nothing currently.

    Within our test these days, they thought this was still due to the IOS system. We found the same e-mail alert will perform differently on different IOS equipment, like IPAD Pro, IPAD Mini or IPhones . The bigger screen, the bigger format. As to use the new email format for the alerts, this is a business decision , and we cannot just roll back to the older one. But we will continue to make the new formats better in the future .

    Anyway, thanks a lot for your patience on this issue , and your prime suggestion on this. Privately , I am so sorry that we didn’t solve the issue for you, hope you can understand we cannot make a decision from support team. We have already tried all our best .

    Funnily enough this was not an issue restricted to iOS devices but they seemed to miss that point

Feedback and Knowledge Base