While task revision from filtered project, next task opened is not from filtered project

[TomaszKozlowski-TomTom]

While doing task's revision editor, after revision completion click 'next' to get another task from the bucket, which is defined by him (as tasks to be reviewed from one project). When next task is opened, it is not from defined/filtered project bucket, as user wanted. With that, user has to jump to the filter again, find another task and continue revision. Task by task, this action has to be repeated.

[TomaszKozlowski-TomTom]

Any news about this bug? @CollinBeczak

[CollinBeczak]

Hmm... Im not 100% following the issue here, there is one workflow that i know of that fits your issue descriptions.

There are 5 different main workflows:
Completion
Revision (You could be talking about this one, but i dont see any filters related to this workflow)
Review (This one loosely matches your description, to me at least)
Inspect
ReadOnly

Image of the current review workflow filters:

Above shows the filters that are used to filter the next available tasks, if the review workflow is what you are referring to than your issue would be fixed by simply adding a project filter, similar to the challenge filter as displayed above.

Let me know if i am miss interpreting something or you have more information. Images of the completion widget would also be useful to identify the specific workflow you are referring to.

[TomaszKozlowski-TomTom]

Hi Collin, as images and explanation below:

• user filters tasks from respective challenge:
  

• after the revision user mark option review next filtered task
  

• next task is not from filtered challenge
  

[CollinBeczak]

Ok, thanks for clarifying that for me. In the optimal scenario we would maintain all the filters applied in the table list.

Right now we only have these 5 filters, indicated in the adjust filters modal:

To resolve your specific issue quickly, i can just add the project filter to that list. Ill get this included in our next deployment, which at latest should be Nov 11th, hopefully i can get it deployed sooner.

[TomaszKozlowski-TomTom]

May be hard as there is no specific project which is checked, we have different ones at one time even.
In this case, we are waiting for the feedback and possible solutions.

Thanks!