https://forge-allura.apache.org/p/allura/tickets/You searched for assigned_to:"pranav"enThu, 22 Aug 2019 14:41:11 -0000https://forge-allura.apache.org/p/allura/tickets/8326/Helm charts for deployment on Kubernetes. Kubernetes has already become a standard for deployment of applications. We already have docker containers for deployment. Configurable helm charts would really ease the process of installation/usage. Info about helm - https://helm.sh/ Info about Kubernetes(K8) - https://kubernetes.io/ @brondsem, Do we already have helm charts? I didn't find them in wiki. If not, I can take it up. Thanks, PranavPranav SharmaThu, 22 Aug 2019 14:41:11 -0000https://forge-allura.apache.org/p/allura/tickets/8326/https://forge-allura.apache.org/p/allura/tickets/8116/One of the basic and maintainable style followed by teams is to create branches related to tickets, and limiting the creation of branches. I think this is a common trend and we should make a feature which would add an option on tickets page to instantly create a new branch from desired base. I believe this would help definitely to manage rogue branches even for frequent committers. Also it helps to directly match what code changes are related to a particular ticket. This would be completely optional and a team can switch it on only if they would want to limit and manage branches. Any suggestions are welcome.Pranav SharmaThu, 01 Nov 2018 13:08:30 -0000https://forge-allura.apache.org/p/allura/tickets/8116/https://forge-allura.apache.org/p/allura/tickets/8115/Various ci services can be supported to manage mordern team development styles. Since they need frequent code push, it helps them to automate testing, and thus would be cool to include in allura projects too.Pranav SharmaThu, 11 Aug 2016 19:45:54 -0000https://forge-allura.apache.org/p/allura/tickets/8115/https://forge-allura.apache.org/p/allura/tickets/8114/Slack has become a popular tool and has good API integrations available. It would be a good integration for users.Pranav SharmaWed, 17 Aug 2016 13:14:26 -0000https://forge-allura.apache.org/p/allura/tickets/8114/https://forge-allura.apache.org/p/allura/tickets/8032/If user does not have primary email some functionality is not working (notifications and stuff). We should set up primary emails for test users. Anytime I'm re-creating my dev environment I'm manually creating emails for at least `root`, `admin` and `test-user-1`. And it's pretty painful, since you need to type email, re-type the password, get confirmation link from server logs. Its low priority, obviously, but would be good to have.Igor BondarenkoFri, 05 Feb 2016 17:33:08 -0000https://forge-allura.apache.org/p/allura/tickets/8032/https://forge-allura.apache.org/p/allura/tickets/8031/The blog tool should have a search option.Dave BrondsemaMon, 11 Jan 2016 19:16:43 -0000https://forge-allura.apache.org/p/allura/tickets/8031/https://forge-allura.apache.org/p/allura/tickets/8029/The submitter of a merge request should be able to change its status to "rejected" (or possibly delete it, but I think that'd be going too far). [#5993] for updating an existing request will help too, but there's still a good case for rejecting your own MR I think. This has been requested by several SF users: https://sourceforge.net/p/forge/feature-requests/254/Dave BrondsemaMon, 14 Mar 2016 20:01:20 -0000https://forge-allura.apache.org/p/allura/tickets/8029/https://forge-allura.apache.org/p/allura/tickets/8018/When an email is confirmed and its the first (only) one, it should automatically become the primary. Right now it is not obvious that you need to take a second step of selecting your one address as the primary. And if you don't do that, you won't get notifications since you don't have a primary address.Dave BrondsemaWed, 02 Dec 2015 20:02:41 -0000https://forge-allura.apache.org/p/allura/tickets/8018/https://forge-allura.apache.org/p/allura/tickets/8005/Subprojects don't get their 'deleted' flag checked, so they are still accessible to non-admins. We should fix this. Also, if there is a deleted subproject and a regular tool of the same name, the regular tool should always take precedence.Dave BrondsemaMon, 28 Mar 2016 16:19:06 -0000https://forge-allura.apache.org/p/allura/tickets/8005/https://forge-allura.apache.org/p/allura/tickets/7949/Followup to [#7925] sort of - at least things noticed from there. Would be nice to show copies and renames a little differently. Not sure how though. On a commit view for git, every parent directly is always listed as a change. This is due to `-t` in the `git.diff_tree` call. We should be able to replace this with `-r` (with some confirmation that `added_paths()` still works right) Commit views should list all files in alphabetical order, rather than grouped by add/remove/etc. Make sure paginating through it works correctly still too.Dave BrondsemaTue, 12 Apr 2016 19:33:21 -0000https://forge-allura.apache.org/p/allura/tickets/7949/https://forge-allura.apache.org/p/allura/tickets/7929/New ticket trackers should have voting enabled be default. Why not?Dave BrondsemaMon, 14 Dec 2015 22:05:44 -0000https://forge-allura.apache.org/p/allura/tickets/7929/https://forge-allura.apache.org/p/allura/tickets/4153/*Originally created by:* roggan87 Hi! Overall I really like the new interface of SourceForge :) I've recently discovered something I'd consider a bug. Please correct me if I'm wrong. I've installed the "blog tool" on our project. The intention is to also use the RSS feed to fetch the blog posts to our website. The problem is that if I edit posts or delete them, it doesn't affect the RSS feed. Is that because of the design of RSS feeds, or simply because that feature is not yet implemented? Thanks, RobertAnonymousMon, 14 Mar 2016 20:25:35 -0000https://forge-allura.apache.org/p/allura/tickets/4153/https://forge-allura.apache.org/p/allura/tickets/1695/Editing a ticket to change the status, milestone, or owner and then having to scroll to the bottom of the page to save the changes could be less painful with an additional save button near the top of the form.John HoffmanWed, 23 Mar 2016 17:57:53 -0000https://forge-allura.apache.org/p/allura/tickets/1695/