In the old PI Square, there were direct links to each post in discussion thread, which was handy for (at least) the following three use cases:
1. Alerts (email or on the site) for new posts on a discussion took you directly to the new post.
2. Alerts (email or on the site) that you were @mentioned in a post took you directly to that post.
3. Ability to reference a particular post that contains the information of interest (e.g., sending a link to customer or coworker to help with a particular issue).
The three use cases above are particularly annoying for longer discussions since the best we can do is link to the discussion, which brings users to the first post and leaves them needing to scroll through all posts to find the one of interest.

Tables are a great way to organize information and I've used them in nearly every blog post. However, on the new PI Square, tables must be copied and pasted from elsewhere (e.g. Excel) and they lose all borders, hyperlinks, and cell fill colours. Content within the table can be edited, but if the author wants to insert, delete, or rearrange any rows or columns, they must make these changes elsewhere and then replace the table in the blog post.

Basically, it is impractical to use tables, which greatly limits the types of blog posts that can be written. Please have better support for tables. Ideally, we would be able to create tables within PI Square and tables copied from elsewhere would retain more of their formatting. I feel that the bare minimum for better table support is getting the table borders to appear.

Right now, the vote numbers on articles are cumulative; they show all of the votes the article has received over the life of the article.

As a result, if there is a problem with an article, say a broken link, then it will get a lot of negative votes. If we fix the problem, then it will still have a lot of negative votes.

If someone sees an article with a lot of negative votes, they will think there is a problem with the article, and they won't trust it.

Instead, the article should show the positive and negative votes for the article version, and below that should be the positive and negative votes for the article as a whole.

With this change, readers will be able to see the story of the article as a whole, the troubled history and the results of the fix.

As an Admin User, I have to manage many hundreds of users on My Team section. When I need to assign a new site to a user or change the user profile (to Download User for instance), I need to find this user across many pages. I cannot search for that user in the filter box since this field only filters for the current page on which they are only few users. If my user is listed further pages down, I need to navigate through all the pages of users before finding this user.

The goal of this feedback is for the search filter box to effectively search across all pages of users so we can find the same in less manual steps.

The page linked below is a major source of confusion for anybody new to PI (e.g. me at the time).
https://www.osisoft.com/pi-system/pi-capabilities/product-list/

The list is not only long, but there is also overlap between the functionality of some products. There are 29 "products" listed, and of those, 9 of them have been superseded:
• Advanced Computing Engine (ACE)
• Batch
• Performance Equations (PE)
• PI BatchView
• PI Interfaces
• PI Interfaces for System Monitoring
• PI ProcessBook
• PI WebParts
• Totalizers

Please revise this page to eliminate mentions of superseded products. This will help both new PI administrators and potential customers get a better overview of the PI system. Quality over quantity.

Currently, for blog posts that are created on the new PI Square, the closest that you can get to deleting a blog post is to delete the content within the blog post, restrict the audience, and archive the blog post or set it to publish in the far future, but you cannot delete the blog post itself or permanently restrict access to a blog post.

Blog posts that were migrated from the old PI Square cannot be edited or deleted at all. Since migrated posts are not always faithful to the original, a user might want to rewrite a migrated blog post and delete the original.

Please allow blog posts of all origins to be deleted.