Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Dashboard] New and pending imaging sessions are unclickable #5461

Closed
kchatpar opened this issue Oct 31, 2019 · 5 comments
Closed

[Dashboard] New and pending imaging sessions are unclickable #5461

kchatpar opened this issue Oct 31, 2019 · 5 comments
Assignees
@Jkat
Labels
Critical to release PR or issue is key for the release to which it has been assigned

Comments

@kchatpar
Copy link

Step 9. Verify that for a user with 'Edit imaging browser QC status' permission the My Tasks panel reports the number of new
scans (i.e. the number of scans on the MRI browser page for which QC status has not been set. Note DCC scans are not
counted in the query as for most projects this is not an acquisition site). Check that site
displayed is always 'All'. Click on this task and verify that you go to the MRI Browser page.
[Automate Test on Travis_CI]

The new and pending imaging sessions leads me to the permission being denied even on the admin account.
@cmadjar
Copy link
Collaborator

cmadjar commented Nov 1, 2019

@Jkat can you please look into this on Monday? Thank you!

@Jkat
Copy link
Contributor

Jkat commented Nov 4, 2019

Need the testing VM to be updated with #5444, otherwise Imaging Browser is in an unloadable state.

@cmadjar
Copy link
Collaborator

cmadjar commented Nov 4, 2019

Actually, it needs #5528 to be reviewed, merged and pulled on testing for the imaging browser to load on testing... Just fixed a separate issue than the one I fixed on #5444...

@driusan driusan added the Critical to release PR or issue is key for the release to which it has been assigned label Nov 5, 2019
@ridz1208
Copy link
Collaborator

ridz1208 commented Nov 5, 2019

I added PR sent but i think it should be closed if its resolved by the 2 PRs above, they are now merged

@cmadjar
Copy link
Collaborator

cmadjar commented Nov 6, 2019

Just tested it and it is working on testing now :).

@cmadjar cmadjar closed this as completed Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Jkat Jkat

Labels
Critical to release PR or issue is key for the release to which it has been assigned
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@driusan @Jkat @cmadjar @ridz1208 @kchatpar