Wrike permalinks are great. They would be better if they led directly to the task page whenever possible.
Issue and the steps to re-create it
Every Wrike permalink that I click requires me to sign in regardless of whether I check for Wrike to "Remember Me." I access Wrike through a corporate single sign-on. The results are cumbersome, although only some of them are within Wrike's control (these are bold):
- Click Wrike permalink
- Enter email address into Single Sign-On login page and submit
- Enter email address into corporate SSO login page and submit (sometimes this page does not display, GOTO 4)
- Enter password into corporate SSO login page and submit
- Collect 2FA from key, enter into authentication page and submit
- Click button asking Wrike to remember my login
- Click button telling Wrike whether or not to open the link in the Wrike app
- The app does not meet my needs, so I decline and then click to open the link in my browser. Note that this page says "You will be redirected in a few moments" yet in my tests never redirects.
A better permalink already exists for web app users
A permalink of the form https://www.wrike.com/workspace.htm#/task-view?id=[id_number] appears to work correctly today. The first attempt to follow a Wrike permalink in this format requires a full login. Subsequent attempts within the same session lead directly to the task record. This is a better user experience.
While this approach does not send the pid and cid parameters to Wrike via the URL, I did not see any difference to the user experience with those parameters missing. Certainly no benefits that warrant, at minimum, a click-type-click-type-click-lookup-type-click-click-click-click process.
The better permalink solution can improve the experience for desktop app users with some changes
The existing permalink probably exists to support the option of opening links directly in the Wrike app. We could solve for the needs of both desktop and web app users by using the better permalink. When using this link, skip the "Opening a link in Wrike App..." page. Instead, trigger the desktop redirect request over the top of the live Wrike web app with the task page already loaded (or a "light" version pre-loaded).
Desktop app users who, for some reason, choose not to have the browser always redirect to the desktop app would be able to see task information more quickly this way. Web app users could also see information immediately and would avoid a redundant click. The impact to desktop app users who have the browser always redirect to the app would not be substantively impacted by this change. (Perhaps the last statement is wrong.)