Post

5 followers Follow
8

Client Name following client.matter number

Prior to being upgraded to 17.2 we could go to Workspace Alias and change our view to have the Client Name following the number. We are now unable to do so with the Examples we were provided. This makes no sense? We need to see the client name next to the number - not having to locate the client name at the end. We need this change added to our Workspace Alias. Actually, it should be the default setting.

Thanks,

Karen Strawn

Status: Planned

Official comment

Avatar

We are currently working on restoring the Workspace Alias functionality. It was not intentional to remove this feature from 17.2, but it was not completed at release time. The Development teams are actively working on this, and we will enable this functionality as soon as it has been completed and certified for release.

Valerie Connell
Comment actions Permalink

Please sign in to leave a comment.

9 comments

1
Avatar

Karen,

If this needs to be a default setting for all users, you can change the workspace name format on the workspace template. New workspaces created going forward will use the new name format. Previous workspaces will need to be deleted and re-created. 

1 vote
Comment actions Permalink
3
Avatar

The answer doesn't make much sense. We have thousands of Workspaces already created. We can't delete and re-create them.

Was this an option in 17.1 but was removed in 17.2?

3 votes
Comment actions Permalink
2
Avatar

This is obviously a bug that needs to be fixed. The option under settings to change the workspace alias is still there in 17.2, however it no longer works. We have out templates set with how the majority of our firm wants the workspaces named, however we have some users that were using this setting as they wanted it displayed differently.

2 votes
Comment actions Permalink
2
Avatar

I agree it's an important bug to fix.  I also see the option in 17.2 but am unable to get it to work as it does in 17.1.

2 votes
Comment actions Permalink
1
Avatar

We encourage you to keep voting for this idea if you wish to see it return to 17.2.

A workspace 'refresh' will also update the workspace name to use the template/default name format (unless the name has already been manually changed by a user). So, if a user sees a workspace with the wrong name format, they can just use the refresh option to correct the name. On another note, workspace alias' are often not liked by some users, because it impacts performance when opening workspaces and loading lists of workspaces. 

1 vote
Comment actions Permalink
3
Avatar

I do not understand why we have to vote to fix something that was broke with an update. If you planned on removing this feature, then it would not still show up as an option under settings. Since it does show up, and no longer works, this should be a bug in the 17.2 version, and not a feature request in the idea bank.

3 votes
Comment actions Permalink
2
Avatar

I'm just going to add my voice to the chorus of dissent. THIS IS  A BUG!!

Not only is it a bug, it was reported as a bug by me at the immediate commencement of the Beta back on the 21st August. I also had assurances from netdocuments at that time, that this was on "the list" of fixes. So here we are, still with no fix and now being suggested it might be a good idea to "upvote it" as a good idea.

We put a percentage of our firm on 17.2 and after that pilot, advised that we would NOT be moving any more users to 17.2 until this ( and not just this specifically this) issue was rectified.

 

We have a large number of matters that share similar if not identical names. Without the ability to identify the client in your list of favourites it is almost impossible to work with and takes far more time to look up and confirm exact matter numbers.

Any new refresh or update should take what works and is useful and build upon that. Not remove KEY features then suggest they might be a good idea to have.

Guess what ?- they were a good idea and were instrumental in the decision to use the netdocuments product in the first instance so please provide the fix at your earliest possible opportunity.

To anyone from netdocuments reading / responding to this could I suggest that you confirm with your product team what is a fix . enhancement or upgrade before suggesting users "upvote" to fix something that has been broken during an "Upgrade".

Should you be unsure, please contact me directly and I will provide you with copies of the videos I created showing the disparity between 17.1 and 17.2 as well as the communications between me and your development / beta team.

 

Thanks

2 votes
Comment actions Permalink