RhodeCode - issues: Issueshttps://issues.rhodecode.com/https://issues.rhodecode.com/favicon.ico?16960560042023-11-13T08:06:05ZRhodeCode - issues
Redmine RhodeCode CE/EE - Task #5705 (New): 5.X - activate update task automatically over rcstackhttps://issues.rhodecode.com/issues/57052023-11-13T08:06:05ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Because rcstack has enabled scheduler by default, we should activate the periodic update check</p>
RhodeCode CE/EE - Task #5697 (New): Improve CI & CD integrationshttps://issues.rhodecode.com/issues/56972023-10-17T16:31:20ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5695 (New): Artifacts - Making artifacts a prime functionalityhttps://issues.rhodecode.com/issues/56952023-10-17T16:28:43ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5694 (New): GIT LFS 2.0https://issues.rhodecode.com/issues/56942023-10-17T16:27:54ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5404 (New): Add an option to detach review rules when deleting an userhttps://issues.rhodecode.com/issues/54042017-11-22T11:23:48ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>In cases there are 100s, and user should be removed we need an explicit option to detach an user from review rules.</p>
<ul>
<li>check what happens then to the old review get changed</li>
<li><p>big fat warning about how it can change old ?</p></li>
<li><p>maybe a replace with X user ?</p></li>
</ul>
<p>again reconsider what this means and if we really should have it !</p>
RhodeCode CE/EE - Task #5400 (New): User group - subgroup supporthttps://issues.rhodecode.com/issues/54002017-11-06T22:00:25ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #5200 (New): investigate search improvementshttps://issues.rhodecode.com/issues/52002017-02-08T00:59:38ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Search in changelog, proper repo filter, re-check syntax.</p>
RhodeCode CE/EE - Task #4669 (New): disable pytest sugar on nix-buildhttps://issues.rhodecode.com/issues/46692016-12-01T12:52:05ZMarcin Kuzminski [CTO]marcin@rhodecode.comRhodeCode CE/EE - Task #4312 (New): Storage location changeshttps://issues.rhodecode.com/issues/43122016-11-28T02:16:25ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Allow custom location per-repository to help fragmentise the source code storage</p>
<ul>
<li>Who will be allowed to change these settings.</li>
<li>What use cases would that support</li>
</ul>
RhodeCode CE/EE - Task #4299 (New): TEMPLATE repo groupshttps://issues.rhodecode.com/issues/42992016-10-26T23:00:16ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Placeholder repo for specs about TEMPLATE repo groups that can be used for creation of pre-defined projects</p>
RhodeCode CE/EE - Task #4290 (New): Allow to transplant the review status to merged commitshttps://issues.rhodecode.com/issues/42902016-10-21T15:00:18ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>In case of pull request merge we currently only leave statuses/comments inside the source repo. For tracability reasons it would be really usefull to push the review statuses back into the origin. At first we should simply support case that only the matched hashes gets transfered the review markers.</p>
RhodeCode CE/EE - Task #4216 (New): [ux, renderers] implement consistent rendering for text fieldshttps://issues.rhodecode.com/issues/42162016-09-06T11:46:39ZLisa Quatmannlisa@rhodecode.com
<p>should be based on settings in _admin/settings/visual<br>
see parent ticket <a class="issue tracker-4 status-1 priority-2 priority-default parent" title="Task: [ux, renderering] Consistent formatting on text fields. (New)" href="https://issues.rhodecode.com/issues/4051">#4051</a></p>
RhodeCode CE/EE - Task #4163 (New): [ce, ee] celery refactor + upgradehttps://issues.rhodecode.com/issues/41632016-08-11T00:55:11ZDaniel Ddaniel@rhodecode.com
<p>Currently celery is being loaded with legacy pylons method and uses magic for configuration setup, we are also on celery 2.2.10 which is old and is lacking features which we need for a 'correct' implementation.</p>
<p>We must:</p>
<ul>
<li>upgrade celery</li>
<li>remove the celerypylons module </li>
<li>make/configure a celery app in load_pyramid_environment()</li>
<li>update all tasks to work with this celeryapp object</li>
</ul>
RhodeCode CE/EE - Task #4051 (New): [ux, renderering] Consistent formatting on text fields.https://issues.rhodecode.com/issues/40512016-06-29T00:00:32ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>Currently we have various fields formatted and wrapped in markdown formatters.</p>
<ul>
<li>For comments we use rst or MD formatter</li>
<li>For Commit messages we use urlify_commit_Message</li>
<li>for readme we use formatter based on the file extensions</li>
<li>for Pull requests we use Markdown/rst formatters</li>
</ul>
<p>Some of those formatters are inconsistent, ie commit messages vs commit commits. We need a quick iteration and find a subset that would make all those behave consistent.</p>
<p>Functionality within text fields which should be included:</p>
<ul>
<li>consistent formatting based on chosen renderer in _admin/settings/visual</li>
<li>@-mentions</li>
<li>issue tracker patterns</li>
<li>linkification of urls</li>
</ul>
RhodeCode CE/EE - Task #4045 (New): File permissionshttps://issues.rhodecode.com/issues/40452016-06-27T11:56:42ZMarcin Kuzminski [CTO]marcin@rhodecode.com
<p>WIP desc, file permissions</p>
<ul>
<li>pattern based</li>
<li>write restriction only</li>
<li>allow/deny semanticks (aka firewall rules pattern)</li>
</ul>