RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042016-03-11T13:34:53ZRhodeCode - issues
Redmine RhodeCode CE/EE - Task #3260 (New): api: expose get_repo_node methodhttps://issues.rhodecode.com/issues/32602016-03-11T13:34:53ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We have get_repo_nodes method while we really need get_repo_node to fetch a single file from repository.</p>
RhodeCode CE/EE - Bug #3250 (New): Posting a comment message is very slow !https://issues.rhodecode.com/issues/32502016-03-08T11:25:06ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>I noticed that posting a message can take few seconds to do. We should check why and fix it :)</p>
Documentation - Task #3093 (New): [API] - update hg/git update pr API. Auto updates PR on pushhttps://issues.rhodecode.com/issues/30932016-01-21T15:30:21ZBrian Butlerbrian@rhodecode.comDocumentation - Task #3092 (New): [RCE, ini] - doc available settings + check tender with Gemalto...https://issues.rhodecode.com/issues/30922016-01-21T15:10:51ZBrian Butlerbrian@rhodecode.comRhodeCode CE/EE - Bug #3022 (New): SVN support with repositories groupshttps://issues.rhodecode.com/issues/30222016-01-06T14:12:06ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>WIP: it seems svn is not supporting repositories groups at the moment.</p>
<p>Will put my findings in this ticket</p>
RhodeCode CE/EE - Task #2944 (New): Bump gunicorn to 19.4 versionhttps://issues.rhodecode.com/issues/29442015-11-23T10:48:09ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Fixes some gevent related issues and other small bugs</p>
RhodeCode CE/EE - Feature #2882 (New): Bulk comment submithttps://issues.rhodecode.com/issues/28822015-11-06T12:25:54ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>When user is reviewing the code, each inline comment is submitted and notification sent to users, this might be annoying. Phabricator has really nice sollution for that. See attached gif</p>
<p>Some specs:</p>
<ul>
<li>users should see their UNSUBMITTED comments in a summary view, and have ability to submit then (see second screenshot)</li>
<li>Page should worn users before leaving that there are unsubmitted comments</li>
<li>Unsubmitted comments should be stored inside DB, but they should not trigger notifications</li>
<li>UN-submitted comments should be only visible to the creator (and super-admins)</li>
<li>UN-submitted comments submit preview pane should be only visible to author, and super-admin. Both of them could submit the comments</li>
<li>Email should be re-formatted with bulk comments, not to spawn multi-emails</li>
<li><p>UN-submitted comments should be marked with a tag, and show text:</p>
<ul>
<li>"this comment is private until you submit it" <submit it should be a link to the preview pane that allows submit</li>
</ul></li>
<li><p>The preview pane should allow to delete comments, and re-create them (Edit them) ?</p></li>
<li><p>I think we Do Need EDIT functionality before this feature</p></li>
</ul>
<p>Phabricator has this, and it's considered very nice option, also Kallithea has this ! Which we cannot be worse :)</p>
RhodeCode CE/EE - Task #2844 (New): Update Bcrypt to a maintained versionhttps://issues.rhodecode.com/issues/28442015-10-27T12:12:46ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We use py-bcrypt-0.4 which is unmaintained.</p>
<p>We should switch to <a href="https://pypi.python.org/pypi/bcrypt/3.1.1" class="external">https://pypi.python.org/pypi/bcrypt/3.1.1</a> which should be fully compatible.</p>
RhodeCode CE/EE - Feature #1457 (New): add allow permissions inheritance on repo groupshttps://issues.rhodecode.com/issues/14572015-03-25T23:00:58ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>WIP description:</p>
<p>Feature request and kind of security enhancement.</p>
<p>When using repo groups we should add a flag to be able that lower creted repos can or cannot inherit permissions from the group. Potentially opening it to other parties</p>
Documentation - Task #737 (New): What is an extra field and how do you add it?https://issues.rhodecode.com/issues/7372015-01-14T13:57:54ZLisa Quatmannlisa@rhodecode.com
<p>Ok, I know the answer to the first part but regular users may not. If you don't have any extra fields, then when you go to the page where you would edit them, you get a message which says "Extra fields are disabled". However, it has no information on how to enable them if one is able to do that.</p>
Documentation - Feature #687 (New): [Integraton ]- Elastic search integrationhttps://issues.rhodecode.com/issues/6872015-01-12T11:07:47ZBrian Butlerbrian@rhodecode.comDocumentation - Task #682 (New): Error Msg guidehttps://issues.rhodecode.com/issues/6822015-01-12T08:56:24ZBrian Butlerbrian@rhodecode.com
<p>We should have a guide that describes the messages, and the actions to take for each one</p>
Documentation - Feature #659 (New): Peer to Peer Failoverhttps://issues.rhodecode.com/issues/6592015-01-08T15:47:01ZBrian Butlerbrian@rhodecode.com
<p>doc this if we have</p>
Documentation - Feature #317 (New): Stylinghttps://issues.rhodecode.com/issues/3172014-11-12T09:44:42ZBrian Butlerbrian@rhodecode.com
<p>Create a Sphinx style for RhodeCode docs</p>
RhodeCode CE/EE - Feature #148 (New): [comments] Add per file and multiline comments in a changesethttps://issues.rhodecode.com/issues/1482014-09-18T17:01:06ZSebastian Kreftskreft@rhodecode.com
<p>Currently it is only possible to comment on a specific line. It would be good to add a per file comment, and even multiline comments. See issue #147.</p>