RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042017-05-30T16:11:23ZRhodeCode - issues
Redmine RhodeCode CE/EE - Task #5326 (Resolved): Public usergroup profilehttps://issues.rhodecode.com/issues/53262017-05-30T16:11:23ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Somehow similar to user profile e.g <a href="https://code.rhodecode.com/_profiles/marcink" class="external">https://code.rhodecode.com/_profiles/marcink</a> but for usergroups.</p>
<ul>
<li>expose a view that shows an usergroup with members, really simple</li>
<li>the view checks usergroup permissions(view at least read required)</li>
<li>we need similar helper as for users which will expose a link to the usergroup profile</li>
</ul>
RhodeCode CE/EE - Task #5270 (New): Comments updateshttps://issues.rhodecode.com/issues/52702017-04-05T12:39:52ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Think about emails sent out on on comments:</p>
<ul>
<li>maybe they shouldn’t be inside both </li>
<li>add more context (TODO resolution)</li>
<li>Maybe thread that would allow reading those ?</li>
</ul>
RhodeCode CE/EE - Task #4238 (Resolved): default reviewers updateshttps://issues.rhodecode.com/issues/42382016-09-22T12:45:15ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Some of my notes</p>
<ul>
<li>it would be good to SAVE the reasons for a reviewer, so it's clear to outsiders which roles other members have. It's good to know "WHO" is the author, who is form the team etc</li>
<li>it'd be good to have "exclude" author option so it's not a possibility that author gets picked to review his own PR</li>
</ul>
RhodeCode CE/EE - Task #4202 (Resolved): Polish the 503.html pagehttps://issues.rhodecode.com/issues/42022016-08-29T16:56:27ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>We have a custom page for NGINX if RhodeCode is down, under: <a href="https://internal-code.rhodecode.com/rhodecode-enterprise-ce/files/default/rhodecode/public/502.html" class="external">https://internal-code.rhodecode.com/rhodecode-enterprise-ce/files/default/rhodecode/public/502.html</a></p>
<p>It is shown via such NGINX entry:</p>
<pre><code> ## custom 502 error page
error_page 502 /502.html;
location = /502.html {
root /path/to/.rccontrol/enterprise-1/static;
}
</code></pre>
<p>It looks very ugly, we should make it look nice and have some more usefull information.</p>
<p>We CANNOT use any variables, images etc. It needs to be PURE html (similar to email templates) but without variables.</p>
RhodeCode CE/EE - Task #4181 (Resolved): Integrations: allow root repos only integrationshttps://issues.rhodecode.com/issues/41812016-08-18T16:09:31ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>I realized that repo groups already allow to have really good control over integrations. I think last missing bit would be a flag that sets the global integrations to work for root level projects only. This would allow to create global catch all for all root level projects, + possible combinations of integrations on repo group level.</p>
<p>THen i could:</p>
<ul>
<li>set global slack integration for all our root projects which are the main ones</li>
<li>set slack integration for <code>u</code> usergroup which is our namespace for forks</li>
<li>skip <code>release</code> group which produces a lot of noise</li>
<li>add any other repo group that we have if we need to.</li>
</ul>
<p>THoughts ?</p>
RhodeCode CE/EE - Task #4180 (Resolved): integrations: possible limit the updates senthttps://issues.rhodecode.com/issues/41802016-08-17T09:42:46ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>based on the amount of comments in this ticket: <a href="https://issues.rhodecode.com/issues/4172" class="external">https://issues.rhodecode.com/issues/4172</a></p>
<p>I wonder, if maybe it's better to aggregate those, and send a list of referenced tickets instead of updating ticket on each commit pushed. In case of large pushes it would almost spam the issue tracker server. After i merged 5-6 commits i got 5-6 emails from redmine.</p>
RhodeCode CE/EE - Task #4179 (New): [ce, ee] refine perms summary listhttps://issues.rhodecode.com/issues/41792016-08-17T02:16:51ZDaniel Ddaniel@rhodecode.com
<p>Sort by name, otherwise it's hard to find repos when list is large.</p>
RhodeCode CE/EE - Task #4147 (New): [ce, ee, docs] Events documentationhttps://issues.rhodecode.com/issues/41472016-08-04T03:52:39ZDaniel Ddaniel@rhodecode.com
<p>We need to add documentation of the json structure that events emit. Would be a good idea to make this auto generated from dummy events so that there is no sync issue between docs/reality.</p>
RhodeCode CE/EE - Feature #4074 (New): Edit review commenthttps://issues.rhodecode.com/issues/40742016-07-06T16:50:33ZTamas Gemes
<p>Currently you can only create and delete your comments during a review.<br>
This is the same for in-code comments and global (commit or pull request) comments.</p>
<p>It would be nice to have an edit feature too.</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.comDocumentation - 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>