Product Idea

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:
There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:
5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------

+1 to all 7 items
May I add
8) text highlighting should be visible in the single item view, that's where a moderator would initiate edits in a natural UX flow. With users only highlighting individual words that happen to repeat in the requirement (paragraph) it's impossible to pinpoint what the comment is in regards.
(also the single item view has a highlight on/off button suggesting there should be highlighting)

------------------------------
Sven Schmidberger
Irdeto
------------------------------

Original Message:
Sent: 03-25-2020 17:24
From: Jonah Caplan
Subject: Review Center optimizations

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:

There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:

maybe the last version I reviewed was v5... there's no way to see that list of items. Sometimes this is preferable over "needs review". Especially in compare view, I can see the diff but not filter out unchanged items.

4) Every new user is extremely confused about the difference between "reply" and "acknowledge" to close comments. The fact that the checkmark is only visible after you've clicked "acknowledge" hides it from new users that this "action" is different and has the effect of closing. Would be nice to have a button to "resolve" that is independent of leaving a comment, similar to gitlab/github etc.

5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------

9) Preview the diff before publishing a new revision

------------------------------
Jonah Caplan
QNX
------------------------------

Original Message:
Sent: 03-26-2020 15:29
From: Sven Schmidberger
Subject: Review Center optimizations

+1 to all 7 items
May I add
8) text highlighting should be visible in the single item view, that's where a moderator would initiate edits in a natural UX flow. With users only highlighting individual words that happen to repeat in the requirement (paragraph) it's impossible to pinpoint what the comment is in regards.
(also the single item view has a highlight on/off button suggesting there should be highlighting)

------------------------------
Sven Schmidberger
Irdeto

Original Message:
Sent: 03-25-2020 17:24
From: Jonah Caplan
Subject: Review Center optimizations

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:

There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:

maybe the last version I reviewed was v5... there's no way to see that list of items. Sometimes this is preferable over "needs review". Especially in compare view, I can see the diff but not filter out unchanged items.

4) Every new user is extremely confused about the difference between "reply" and "acknowledge" to close comments. The fact that the checkmark is only visible after you've clicked "acknowledge" hides it from new users that this "action" is different and has the effect of closing. Would be nice to have a button to "resolve" that is independent of leaving a comment, similar to gitlab/github etc.

5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------

10) disable deadlines for a review

------------------------------
Jonah Caplan
QNX
------------------------------

Original Message:
Sent: 03-26-2020 15:32
From: Jonah Caplan
Subject: Review Center optimizations

9) Preview the diff before publishing a new revision

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 03-26-2020 15:29
From: Sven Schmidberger
Subject: Review Center optimizations

+1 to all 7 items
May I add
8) text highlighting should be visible in the single item view, that's where a moderator would initiate edits in a natural UX flow. With users only highlighting individual words that happen to repeat in the requirement (paragraph) it's impossible to pinpoint what the comment is in regards.
(also the single item view has a highlight on/off button suggesting there should be highlighting)

------------------------------
Sven Schmidberger
Irdeto

Original Message:
Sent: 03-25-2020 17:24
From: Jonah Caplan
Subject: Review Center optimizations

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:

There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:

maybe the last version I reviewed was v5... there's no way to see that list of items. Sometimes this is preferable over "needs review". Especially in compare view, I can see the diff but not filter out unchanged items.

4) Every new user is extremely confused about the difference between "reply" and "acknowledge" to close comments. The fact that the checkmark is only visible after you've clicked "acknowledge" hides it from new users that this "action" is different and has the effect of closing. Would be nice to have a button to "resolve" that is independent of leaving a comment, similar to gitlab/github etc.

5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------

+1; Always preview, also at review creation before sending emails.
And provide also a clear(er) warning when Review filter selects no item.

------------------------------
Christian Binard
ON semiconductor
Belgium
------------------------------

Original Message:
Sent: 03-26-2020 15:32
From: Jonah Caplan
Subject: Review Center optimizations

9) Preview the diff before publishing a new revision

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 03-26-2020 15:29
From: Sven Schmidberger
Subject: Review Center optimizations

+1 to all 7 items
May I add
8) text highlighting should be visible in the single item view, that's where a moderator would initiate edits in a natural UX flow. With users only highlighting individual words that happen to repeat in the requirement (paragraph) it's impossible to pinpoint what the comment is in regards.
(also the single item view has a highlight on/off button suggesting there should be highlighting)

------------------------------
Sven Schmidberger
Irdeto

Original Message:
Sent: 03-25-2020 17:24
From: Jonah Caplan
Subject: Review Center optimizations

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:

There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:

maybe the last version I reviewed was v5... there's no way to see that list of items. Sometimes this is preferable over "needs review". Especially in compare view, I can see the diff but not filter out unchanged items.

4) Every new user is extremely confused about the difference between "reply" and "acknowledge" to close comments. The fact that the checkmark is only visible after you've clicked "acknowledge" hides it from new users that this "action" is different and has the effect of closing. Would be nice to have a button to "resolve" that is independent of leaving a comment, similar to gitlab/github etc.

5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------

a possible 11) i've not a been able to identify a way to delete requirements during review. Is this possible? Or do you have to go back to the project interface to delete requirements the review team decided were superfluous?

------------------------------
Jamie Wardlaw
Lucid Motors
------------------------------

Original Message:
Sent: 03-30-2020 03:54
From: Christian Binard
Subject: Review Center optimizations

+1; Always preview, also at review creation before sending emails.
And provide also a clear(er) warning when Review filter selects no item.

------------------------------
Christian Binard
ON semiconductor
Belgium

Original Message:
Sent: 03-26-2020 15:32
From: Jonah Caplan
Subject: Review Center optimizations

9) Preview the diff before publishing a new revision

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 03-26-2020 15:29
From: Sven Schmidberger
Subject: Review Center optimizations

+1 to all 7 items
May I add
8) text highlighting should be visible in the single item view, that's where a moderator would initiate edits in a natural UX flow. With users only highlighting individual words that happen to repeat in the requirement (paragraph) it's impossible to pinpoint what the comment is in regards.
(also the single item view has a highlight on/off button suggesting there should be highlighting)

------------------------------
Sven Schmidberger
Irdeto

Original Message:
Sent: 03-25-2020 17:24
From: Jonah Caplan
Subject: Review Center optimizations

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:

There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:

maybe the last version I reviewed was v5... there's no way to see that list of items. Sometimes this is preferable over "needs review". Especially in compare view, I can see the diff but not filter out unchanged items.

4) Every new user is extremely confused about the difference between "reply" and "acknowledge" to close comments. The fact that the checkmark is only visible after you've clicked "acknowledge" hides it from new users that this "action" is different and has the effect of closing. Would be nice to have a button to "resolve" that is independent of leaving a comment, similar to gitlab/github etc.

5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------

12) paging for feedback with page size selection

------------------------------
Jonah Caplan
QNX
------------------------------

Original Message:
Sent: 03-30-2020 12:08
From: Jamie Wardlaw
Subject: Review Center optimizations

a possible 11) i've not a been able to identify a way to delete requirements during review. Is this possible? Or do you have to go back to the project interface to delete requirements the review team decided were superfluous?

------------------------------
Jamie Wardlaw
Lucid Motors

Original Message:
Sent: 03-30-2020 03:54
From: Christian Binard
Subject: Review Center optimizations

+1; Always preview, also at review creation before sending emails.
And provide also a clear(er) warning when Review filter selects no item.

------------------------------
Christian Binard
ON semiconductor
Belgium

Original Message:
Sent: 03-26-2020 15:32
From: Jonah Caplan
Subject: Review Center optimizations

9) Preview the diff before publishing a new revision

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 03-26-2020 15:29
From: Sven Schmidberger
Subject: Review Center optimizations

+1 to all 7 items
May I add
8) text highlighting should be visible in the single item view, that's where a moderator would initiate edits in a natural UX flow. With users only highlighting individual words that happen to repeat in the requirement (paragraph) it's impossible to pinpoint what the comment is in regards.
(also the single item view has a highlight on/off button suggesting there should be highlighting)

------------------------------
Sven Schmidberger
Irdeto

Original Message:
Sent: 03-25-2020 17:24
From: Jonah Caplan
Subject: Review Center optimizations

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:

There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:

maybe the last version I reviewed was v5... there's no way to see that list of items. Sometimes this is preferable over "needs review". Especially in compare view, I can see the diff but not filter out unchanged items.

4) Every new user is extremely confused about the difference between "reply" and "acknowledge" to close comments. The fact that the checkmark is only visible after you've clicked "acknowledge" hides it from new users that this "action" is different and has the effect of closing. Would be nice to have a button to "resolve" that is independent of leaving a comment, similar to gitlab/github etc.

5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------

13) Search by project ID in TOC/Search view

------------------------------
Jonah Caplan
QNX
------------------------------

Original Message:
Sent: 04-06-2020 14:44
From: Jonah Caplan
Subject: Review Center optimizations

12) paging for feedback with page size selection

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 03-30-2020 12:08
From: Jamie Wardlaw
Subject: Review Center optimizations

a possible 11) i've not a been able to identify a way to delete requirements during review. Is this possible? Or do you have to go back to the project interface to delete requirements the review team decided were superfluous?

------------------------------
Jamie Wardlaw
Lucid Motors

Original Message:
Sent: 03-30-2020 03:54
From: Christian Binard
Subject: Review Center optimizations

+1; Always preview, also at review creation before sending emails.
And provide also a clear(er) warning when Review filter selects no item.

------------------------------
Christian Binard
ON semiconductor
Belgium

Original Message:
Sent: 03-26-2020 15:32
From: Jonah Caplan
Subject: Review Center optimizations

9) Preview the diff before publishing a new revision

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 03-26-2020 15:29
From: Sven Schmidberger
Subject: Review Center optimizations

+1 to all 7 items
May I add
8) text highlighting should be visible in the single item view, that's where a moderator would initiate edits in a natural UX flow. With users only highlighting individual words that happen to repeat in the requirement (paragraph) it's impossible to pinpoint what the comment is in regards.
(also the single item view has a highlight on/off button suggesting there should be highlighting)

------------------------------
Sven Schmidberger
Irdeto

Original Message:
Sent: 03-25-2020 17:24
From: Jonah Caplan
Subject: Review Center optimizations

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:

There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:

maybe the last version I reviewed was v5... there's no way to see that list of items. Sometimes this is preferable over "needs review". Especially in compare view, I can see the diff but not filter out unchanged items.

4) Every new user is extremely confused about the difference between "reply" and "acknowledge" to close comments. The fact that the checkmark is only visible after you've clicked "acknowledge" hides it from new users that this "action" is different and has the effect of closing. Would be nice to have a button to "resolve" that is independent of leaving a comment, similar to gitlab/github etc.

5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------

14. Provide a summary/description for the review that you can see at the top of the review, similar to gitlab/github/reviewboard etc. Most people don't read the email notifications, so  it would be useful having a place at the top of the review that can explain about the changes or maybe provide a link to a related report where it's much harder to miss.

------------------------------
Jonah Caplan
QNX
------------------------------

Original Message:
Sent: 04-14-2020 11:37
From: Jonah Caplan
Subject: Review Center optimizations

13) Search by project ID in TOC/Search view

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 04-06-2020 14:44
From: Jonah Caplan
Subject: Review Center optimizations

12) paging for feedback with page size selection

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 03-30-2020 12:08
From: Jamie Wardlaw
Subject: Review Center optimizations

a possible 11) i've not a been able to identify a way to delete requirements during review. Is this possible? Or do you have to go back to the project interface to delete requirements the review team decided were superfluous?

------------------------------
Jamie Wardlaw
Lucid Motors

Original Message:
Sent: 03-30-2020 03:54
From: Christian Binard
Subject: Review Center optimizations

+1; Always preview, also at review creation before sending emails.
And provide also a clear(er) warning when Review filter selects no item.

------------------------------
Christian Binard
ON semiconductor
Belgium

Original Message:
Sent: 03-26-2020 15:32
From: Jonah Caplan
Subject: Review Center optimizations

9) Preview the diff before publishing a new revision

------------------------------
Jonah Caplan
QNX

Original Message:
Sent: 03-26-2020 15:29
From: Sven Schmidberger
Subject: Review Center optimizations

+1 to all 7 items
May I add
8) text highlighting should be visible in the single item view, that's where a moderator would initiate edits in a natural UX flow. With users only highlighting individual words that happen to repeat in the requirement (paragraph) it's impossible to pinpoint what the comment is in regards.
(also the single item view has a highlight on/off button suggesting there should be highlighting)

------------------------------
Sven Schmidberger
Irdeto

Original Message:
Sent: 03-25-2020 17:24
From: Jonah Caplan
Subject: Review Center optimizations

This is a collection of gripes from various users after doing some signficant review work in Jama. Overall first time users are having a fairly positive experience in being able to target comments in more detail but there are some recurring paint points.
1) In a large review the page is constantly updating with the backend which can a frustratingly long time. Every time I accept an item it takes over 15 seconds for the page to update:

There should really be some caching and a refresh button similar to most other views. The 15 second time in itself is a bit frustrating even for initial page load.

2) A lot of actions trigger a reset in how the page looks, e.g. I'm in approver view, then I do something, now I'm back in moderator view, or the filter has disappeared, or I'm no longer in compare view, or all o the above.

3) the button to filter items should be for any version and not hard coded to the last version:

maybe the last version I reviewed was v5... there's no way to see that list of items. Sometimes this is preferable over "needs review". Especially in compare view, I can see the diff but not filter out unchanged items.

4) Every new user is extremely confused about the difference between "reply" and "acknowledge" to close comments. The fact that the checkmark is only visible after you've clicked "acknowledge" hides it from new users that this "action" is different and has the effect of closing. Would be nice to have a button to "resolve" that is independent of leaving a comment, similar to gitlab/github etc.

5) The combination of #1 and #2 are worth calling out specifically when a user needs to flip back and forth frequently between the feedback and review views. Why aren't these tabs like in the main project view that I can flip without triggering a reload? Or If I am reading feedback and click on the item then it takes me to the single item view, then there's no way for me to get back to the same place in the feedback view and if I click 'back to review' then I get the 15 second load time.

6) Changing the set of items in a review. Sending individual items for review is very useful, unless you need to add another item. Workaround right now is to tag them, then create a filter for the tag, then send the filter for review. The backend should handle all that and just let me arbitrarily change the selection for what is being reviewed when publishing a new revision.

7) Let users control what fields they see in the review. That little gear icon in almost every other view is very useful!

​​Thanks!

------------------------------
Jonah Caplan
QNX
------------------------------