Client requests that a project can be made Read Only much like the Archive feature, which he has tried, but it should be searchable at least within a group.
@kforner I can't help but feel that this is creating a feature for a problem that doesn't really exist, i.e. I don't see how someone would commit by mistake.
Alternatively, you can simply create a group with projects that you want to be read-only and use the 'share with group' feature to give people access to it, where you set the max access level to reporter.
That's also a bit clunky, so what about making archived projects searchable? I'll investigate if this is viable and love to hear your thoughts.
That's also a bit clunky, so what about making archived projects searchable?
I'd reformulate: what about not hiding archived projects ? Or list them with a visual attribute. I did not want to break other users' workflow, that's why I proposed a "read-only" feature.
My use case: When we close a project, we transfer it into the "archived" group, it is then backed-up using a different process, and we did want to accidentally commit new changes, but we still want to list the project, and view files and history.
I think that being able to search for archived project is useful but having them show up with all other projects might pollute the search results. Is it possible to make them searchable only within a group? How about adding a filter to search for archived projects only? The visual differentiation is also a good idea, what do you think @creamzy?
@JobV@balameb we need t come up with visual differentiation anyway, if we want to show archived projects as results. For me the question is where should we make this query possible?
Dashboard
Inside a group
Inside a group NEW
@JobV@dzaporozhets what do you think about most appropriate placement for this filter/switcher - dashboard level or group level, or both?
I would suggest this approach for refining search results for a list of projects, it covers archive issues and gives extra handy author sorting - mainly all you need to narrow your search results
Also I assume we need some distinguishing between archived/nonarchived projects - I've added icon on the right side of a project line prior to the star counter. Please share your concerns.
What's your feedback on naming nonarchived projects as active
What's your feedback on naming nonarchived projects as active
I'm not completly against it, but it could become confusing for the user.
For example a project that hasn't seen any activity in the last 5 years would still be labeled as active like this.
I can see a use case where i'm searching for a specific topic, but want to filter out all inactive projects that are not really maintained. (We currently don't offer this, but it would be confusing to rename this later)