Is anyone else frustrated with Jama's poor user experience? It often feels like they don't consult any real users as part of their design process.
A good example of this is the new 'include item attachments' in the initiate review process.
A key element of this new feature is that the reviewers/approvers must have at least read ('collaborator') access to the items within the review to download the attachments. The review moderator can't grant these permissions… only a Jama admin can do that.
How are moderators supposed to know this?
There is nothing next to the check box to explain this:
There's nothing in the help section about permissions:
Even the release notes don't explain how it works:
Our group of 50+ users have been ticking this box without realising that their reviewers don't have the correct permissions. And why would they? There's no warning… no explanation.
And to make it worse the reviewers still see the attachments in the review:
But when they click on it they get this very unhelpful error message:
This could have been handled so much better. Personally, I think that moderators should have an option to grant reviewers permission when they include the attachments. If this isn't an option, then at the very least there should be some on-screen messaging warning that some reviewers won't be able to view the attachments. Or at least bother to update the help section with some decent documentation about how this feature works.As an idea, maybe something like this when selecting users:
Hi Kevin. Thanks for the response. It's good to hear that you're listening to users and some of the recent UI updates to the navigations menus are a good start to getting Jama's user experience to a better place.
I'm just frustrated that you would release a new feature that seems so poorly implemented. Jama seems to place the burden on its users to research the intricacies of how its system works instead of making features intuitive (or at least providing clear on-screen messaging).
This new feature was causing so much confusion that I had to write up some documentation myself to explain to our users how this feature works (see below). It's taken quite a bit of time to deal with.
I'll definitely sign up to your research list… I'd be happy to provide input!
HEADQUARTERS|135 SW Taylor Suite 200, Portland, Oregon, 97204