Ticket search results

Allura Code Viewer: provide more information in History view

Anonymous — Thu, 20 Aug 2015 22:07:54 -0000

*Originally created by:* dcommander This is one of several tickets I am creating to log what I feel are shortcomings in the new (Allura) code viewer relative to the old (ViewVC) code viewer. In all of these cases, simply providing a way for users to continue using ViewVC would be an acceptable workaround. In the History view of the new code viewer, only very limited information is displayed, and in particular, long commit messages are cut off. Compare: http://libjpeg-turbo.svn.sourceforge.net/viewvc/libjpeg-turbo/branches/1.2.x/BUILDING.txt?view=log with https://sourceforge.net/p/libjpeg-turbo/code/HEAD/log/?path=/branches/1.2.x/BUILDING.txt The ViewVC log view has the following features that the new Allura log view lacks: -- Displays the complete commit message -- Displays same in a fixed-width font, so pre-formatted commit messages are displayed correctly -- Displays date *and* time of commit (as well as relative time since commit) -- Provides view/download links for each revision (NOTE: in this case, "download" actually means "view directly in browser." It isn't the same as the "download" feature you already have implemented. See ticket #5227 regarding the desire to provide a "view in browser" mode for the new code viewer.) Suggest having three links: "view" that pops up the file in your existing code viewer, "download" that literally downloads the file, and "view in browser" that views the file directly in the browser without downloading. -- File length in bytes

We should populate the "Other ways to get help" for /support on allura projects NEEDS INI

Chris Tsai — Thu, 20 Aug 2015 22:07:53 -0000

Currently, Allura tools don't show up in the "Other ways to get help" section of the /support page, we should add that.

New GIT RSS feed has superflous title string. [ss2482]

Chris Tsai — Thu, 20 Aug 2015 22:07:54 -0000

[forge:site-support:#2482] >Hi, the recent upgrade to the new SourceForge format of my project page (SleepyHead) has resulted in a few problems. >The RSS feed under code shows "New Commit" for every title even though it's a feed of git commits. It really should show the first line of the GIT commit comments. >Makes the RSS feed practically useless for quick review to see who's posting what. >Please change this if possible.. >[Screenshot](https://sourceforge.net/p/forge/site-support/2482/attachment/Screen%20Shot%202013-01-19%20at%2011.02.14%20AM.png) as how it used to be. Very useful.. Now it's just 5 rows of New Commit. Boring. Sounds like a good change to me.

Ticket stats for allura projects

Dave Brondsema — Wed, 15 Apr 2015 05:37:41 -0000

Provide ticket stats within Allura Convert classic tickets stats into that new Allura stats viewer. There is a basic implementation already. For example: https://sourceforge.net/p/test-brondsem/bugs/stats/?dates=2012-01-01+to+2012-08-01

Forum stats for allura projects

Dave Brondsema — Thu, 20 Aug 2015 22:07:52 -0000

Provide forums stats within Allura. Also, convert classic forum stats into that new Allura stats viewer.

Allow additional fields to be shown on bug tracker

Anonymous — Thu, 20 Aug 2015 22:07:55 -0000

*Originally created by:* orexx While learning how to work with the bug tracking system, the following fields (from the previous Sourceforge system) serve an important purpose and are not present currently. So please add the ability to display the following fields in the bug tracker: - the column "reported_by_s", - a field/column "reported_date_dt" and - a field/column "mod_date_dt.

SCM statistics for Allura projects

Chris Tsai — Tue, 19 Jan 2021 07:12:25 -0000

Provide SCM stats within Allura. Also, convert classic SCM stats into that new Allura stats viewer.

Need admin privileges in allura interface to add files (sometimes?) [26087]

Chris Tsai — Sat, 03 Jan 2015 11:32:18 -0000

https://sourceforge.net/apps/trac/sourceforge/ticket/26087 Tested on my [fancypants](/p/fancypants/) test project. With my (much older) "sillygoose" test account, I can add files via the web interface regardless of whether that's an admin or just developer. Whereas my "chompchompgoat" test account (created today), I can only add files if he's listed as an admin. I tried adding "Developer" to "Configure" on the Downloads tool permissions, and that didn't make a difference. [#2242] seems related?

Move tickets between ticket tools/projects

Chris Tsai — Thu, 20 Aug 2015 22:07:56 -0000

It would be useful to be able to move tickets between different ticket instances. Specific use cases for support would be: 1) moving confirmed bug reports to engr for further eval/processing. So we can maintain separate ticket queues without needing to manage duplicate tickets. 2) moving tickets that should have been logged to a project instead. I think both these cases could be covered by only allowing users with admin(?) permissions on both tickets instances to move tickets between them. *We should also consider auto-forwarding from the old ticket URL and not re-using the ticket number after a ticket has been moved.* Let's not do this yet. But we do need to figure out how to clean up old references to the old artifact path (e.g. solr and artifact references) *Another concern is how to handle custom fields/statuses that aren't shared by both tickets instances.* We should just drop those fields/values if they can't be converted. But we should put a comment on the ticket about the conversion and include the full URL of the prior ticket and also insert all the fields/values that couldn't be converted. The ticket artifact should stay the same, so that subscriptions and other stuff are preserved.

svn import with invalid cert

Dave Brondsema — Thu, 20 Aug 2015 22:07:54 -0000

I'm pretty sure this error is due to the remote repo having an invalid ssl certificate. We should allow invalid certs. ~~~~ Traceback (most recent call last): File "/var/local/allura/Allura/allura/tasks/repo_tasks.py", line 31, in clone cloned_from_url) File "/var/local/allura/Allura/allura/model/repository.py", line 227, in init_as_clone self._impl.clone_from(source_url) File "/var/local/allura/ForgeSVN/forgesvn/model/svn.py", line 176, in clone_from subprocess.check_call(['svnsync', 'init', self._url, source_url]) File "/usr/lib64/python2.7/subprocess.py", line 511, in check_call raise CalledProcessError(retcode, cmd) CalledProcessError: Command '['svnsync', 'init', u'file:///svn/p/sagittarius/code', u'https://repo.smilfinken.net/projects/sagittarius']' returned non-zero exit status 1 ~~~~

Search for open tickets only

Anonymous — Thu, 20 Aug 2015 22:07:54 -0000

*Originally created by:* cweiske I wanted report a bug about the label count being wrong in my project, so I searched the allura tickets for "label count" and got 207 results. Many of those 207 tickets were closed. I don't want to see the closed ones because if they are closed, then I would not see the issue in allura. So I'd like to get a way to filter my search further by showing open tickets only.

Users need a way to backup allura data [idt 824] NEEDS INI

Chris Tsai — Thu, 20 Aug 2015 22:07:20 -0000

https://sourceforge.net/apps/ideatorrent/sourceforge/ideatorrent/idea/824/ >SF clearly says that the backup of the project data is left to project admins: >https://sourceforge.net/apps/trac/sourceforge/wiki/Backup%20your%20data >Fine. >However, there is currently no way to backup the SF2.0 tools, for instance the data from the ticket tool. Backups would be the first step, then a way to restore (though we never offered that part in SF classic to my knowledge)?

Add additional free form text blocks to tracker tool

John Hoffman — Thu, 20 Aug 2015 22:07:55 -0000

- One text area that's displayed on the ticket creation page - Another text area that's displayed on the ticket browse/search/etc screen

Ticket tools should have a pending/overdue setting

John Hoffman — Fri, 05 Dec 2014 11:16:24 -0000

- Add additional pending/overdue preferences to the admin interface - sfx trackers at the tool level define 'days until overdue' and 'days until pending' - Tickets that have not been updated in days have their status changed to Pending - Pending tickets that are not updated in days are Closed

Allow tool level notifications to custom e-mail address

John Hoffman — Thu, 20 Aug 2015 22:07:57 -0000

- sfx allows you to send 'new tickets' or 'all changes' to a specified e-mail address per tracker

Enable/disable per forum anon posting privs

John Hoffman — Thu, 20 Aug 2015 22:07:54 -0000

Similar to Jenny's work on the per forum developer view only toggle, we want to be able to restrict anon posting to forums at the forum, rather than tool, level. So, the 3 options for a forum would be - `*anon` can unmoderated post, and read - `*authenticated` can unmoderated post, `*anon` can only read - Member can read/post/unmoderated post, `*anon and *auth` cannot read/post/unmoderated post

Add an option to restrict forums within the discussion tool to be member/developer visible only

John Hoffman — Thu, 20 Aug 2015 22:07:53 -0000

Rather than create a tool/mount point for each SFX forum (some projects have 10-50 forums), all we need to be able to do is restrict a forum within the tool to be visible by developers only.

Update discussion tool to allow all posts to be sent to an email address

John Hoffman — Thu, 20 Aug 2015 22:07:54 -0000

* i.e. a mailing list monitoring a web based forum * was: [#2789] usage: 4,256 > 5 posts 2,798 > 15 posts out of 1,962,253 forums

Show recent project activity

Dave Brondsema — Fri, 13 Mar 2015 23:07:34 -0000

Probably can use zarkov as an event source, but needs to be stored differently. Classic projects have this available at the /develop page.

RFE: code snapshots for allura repos

Chris Tsai — Thu, 20 Aug 2015 22:07:55 -0000

It can be very useful sometimes for users to be able to just download a source repository without having to install an SCM client. ViewVC supports this for CVS and SVN, for example, see the "Download GNU tarball" link here: http://easymock.svn.sourceforge.net/viewvc/easymock/ Gitweb also has that feature, they call it "snapshots", though siteops have currently disabled it on our gitweb instance since they found it to be causing load issues on the servers. In any case though, I think this would be a worthwhile addition to the allura code browser.

Send SCM updates to a mailing list [21171]

Chris Tsai — Thu, 20 Aug 2015 22:07:54 -0000

Classic forge repos can (through hooks) be set to send updates to a mailinglist (often used with "-devel" lists). There doesn't seem to be a way to do that with allura repos.

Add a UI for importing SVN repos

Dave Brondsema — Thu, 20 Aug 2015 22:07:56 -0000

The code is as easy as: ~~~~ p.install_app('SVN', init_from_url=repo['location']) ~~~~ But we should have a UI for it. Probably something that works *after* you install the tool would be best. And make sure the tool goes into 'analyzing' state or something like that, so users know that it's working on it. Git and hg can be initialized the same way, but that's not really necessary since they're distributed SCMs and you can push the repo yourself. (classic SVN import happens from the shell: http://sourceforge.net/apps/trac/sourceforge/wiki/SVN%20adminrepo)

Enable forum-level subscriptions

Dave Brondsema — Thu, 20 Aug 2015 22:07:57 -0000

Currently only thread-level subscriptions are available. Forum-level would be very useful. In ForgeDiscussion/forgediscussion/controllers/root.py def discuss() there is code to do it, but that code is never used. The thread-level form submits to discuss() from Allura/allura/controllers/discuss.py

SCM - Write a 'blame' interface for SCM file views

Rick Copeland — Sat, 24 Jan 2015 00:32:28 -0000

At a minimum, this should handle tracking across merge commits