search

dwrensha / gitlab-sandstorm

GitLab as a Sandstorm app
20 stars 8 forks source link

Issues not visible when sharing access in Sandstorm for Work #18

Closed germakoci closed 8 years ago

germakoci commented 8 years ago

I'm using a gitlab grain on sandstorm for work, share it with others and the issues are not visible to any other user (no matter if master, reporter or guest).

dwrensha commented 8 years ago

Ouch. I can reproduce this problem. I'm not sure what's going wrong. The grain owner can see issues but apparently nobody else can, unless they navigate directly there (e.g. /gitlab/repo/issues/1 ).

Thanks for the report!

dwrensha commented 8 years ago

Current guess: somehow all issues are defaulting to being "confidential".

germakoci commented 8 years ago

thanks @dwrensha - I guess this goes only for the grain owner, right? since I have issues shared by one of the collaborators to the grain, and I can see them.

btw, is there a place to change these settings ?

dwrensha commented 8 years ago

OK, I've published a new release that should fix this problem. You can download the new version from the app market or just wait a day to auto-upgrade.

The fix is here. The problem had to do with the fact that we're using SQLite, while upstream only officially supports Postgres and MySql.

btw, is there a place to change these settings ?

In a "public" gitlab repo, there is a checkbox in the "new issue" form that allows you to make the issue confidential. Since repos in the Sandstorm port are always "private", this checkbox does not show up.

germakoci commented 8 years ago

oau, that was fast, thanks! have the new version, it works.

The problem had to do with the fact that we're using SQLite, while upstream only officially supports Postgres and MySql.

I get it: I heard that before, I guess it was for PaperWork inside sandstorm