<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for assigned_to:"kadams54"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:57 -0000</lastBuildDate><item><title>Milestone containing ":" breaks Tracker [21436]</title><link>https://forge-allura.apache.org/p/allura/tickets/2714/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/21436

&gt; When I was adding a milestone ("core 0:alpha") to my project (LostWave) it crashed the whole Tickets module. I tried setting it up again, but it still crashes when I add anything with a ":" in it...

I was able to repro on a sandbox. On a forge project, install Tracker, go to Tracker, click 'Edit Milestones', create a milestone with title = 'core 0:alpha' (leave other fields blank), and click Save. After page refresh, click on 'Tickets' icon in the nav to go back to Ticket home - you'll get a 500 error. Now go back to project home and you'll see that the Tracker tool has disappeared from the nav.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2714/</guid></item><item><title>deleting a project does not delete its sub-projects</title><link>https://forge-allura.apache.org/p/allura/tickets/2332/</link><description>for example, note the /p/ludvig/ludvigj project.  /p/ludvig does not exist</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wolf</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2332/</guid></item><item><title>Write script to fix missing subroles in production</title><link>https://forge-allura.apache.org/p/allura/tickets/2330/</link><description>After [#2264] is finished, need a script to repair any damage done in prod.

~~~~~
"""
For projects:
    * Admin role.roles should contain Developer, and Developer only
    * Developer role.roles should contain Member, and Member only

For project.users:
    * user.project_role().roles, if it contains Admin, should not contain
      Developer or Member
    * user.project_role().roles, if it contains Developer, should not contain
      Member
"""
~~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Van Steenburgh</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2330/</guid></item><item><title>"Mark as Spam" shouldn't be present for anon users</title><link>https://forge-allura.apache.org/p/allura/tickets/2292/</link><description>On the thread view of forum pages.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2292/</guid></item><item><title>Notifications from wiki page rename have wrong subject</title><link>https://forge-allura.apache.org/p/allura/tickets/2279/</link><description>"$username renamed page $new to $old" should be "$username renamed page $old to $new"</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2279/</guid></item><item><title>Title text for neighborhood icon</title><link>https://forge-allura.apache.org/p/allura/tickets/2232/</link><description>When neighborhood icons are displayed on the upper right of project pages, put title/alt text "Return to {{neighborhood_name}} Neighborhood"</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2232/</guid></item><item><title>Icon for Ticket-category won't appear [19737]</title><link>https://forge-allura.apache.org/p/allura/tickets/2229/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/19737

&gt;I had an issue with creating some milestones and ended in deleting the whole Ticket-tool, and reinstall it. But now the icon won't appear. Not a big issue, but I thought it might be of help to report small bugs as well with this beta-version. Great stuff, btw!

&gt;Hope you could fix this for me!

&gt;https://sourceforge.net/p/episodecleaner/tickets</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2229/</guid></item><item><title>create subproject of a user project is broken</title><link>https://forge-allura.apache.org/p/allura/tickets/2148/</link><description>~~~~
[Fri May 20 16:42:54 2011] [error] [client 127.0.0.1] File '/home/wolf/wolf-5014/forge-classic/sfx/sfx_main.py', line 180 in register_subproject
[Fri May 20 16:42:54 2011] [error] [client 127.0.0.1]   ug_name = self.api.create(user, project.neighborhood, project.shortname + '/' + name)
[Fri May 20 16:42:54 2011] [error] [client 127.0.0.1] TypeError: create() takes at least 5 arguments (4 given)
~~~~

This may affect subprojects of regular projects as well</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wolf</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2148/</guid></item><item><title>'projects' macro is very slow</title><link>https://forge-allura.apache.org/p/allura/tickets/2094/</link><description>https://sourceforge.net/adobe/wiki/Projects/ loads very slowly</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2094/</guid></item><item><title>ticket counts on ticket homepage and milestone page are sometimes wrong</title><link>https://forge-allura.apache.org/p/allura/tickets/2080/</link><description>as reported by Dave in [#2059]:

&gt; Also on this page (and the mongo-ified milestone lists) the "Showing 116 results of 116" numbers are incorrect.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wolf</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2080/</guid></item><item><title>Let tab or maybe shift-tab insert 4 spaces</title><link>https://forge-allura.apache.org/p/allura/tickets/1989/</link><description>You should allow indenting the content with the \[Tab\] or \[Shift\] + \[Tab\] key 
  (markdown consistently use it), which is always better, than to bother the space key ;)
  Consider this jQuery Plugin: &lt;http://teddevito.com/demos/textarea.html&gt;


Assuming this plugin works well on all browsers without performance issues</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1989/</guid></item><item><title>Fix missing icon in allura theme for wiki page undelete</title><link>https://forge-allura.apache.org/p/allura/tickets/1908/</link><description>The HTML is right, but there is no icon displayed (and thus I can't undelete wiki pages).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1908/</guid></item><item><title>Test &amp; fix "include" macro</title><link>https://forge-allura.apache.org/p/allura/tickets/1907/</link><description>e.g. https://sourceforge.net/adobe/cairngorm/wiki/Cairngorm/ 

Add an example in our Markdown help.

Communicate with adobe when fixed in prod.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1907/</guid></item><item><title>make milestone page use only mongo queries, no SOLR</title><link>https://forge-allura.apache.org/p/allura/tickets/1826/</link><description>Make sure this special milestone field has a mongo index, so we can do counts effeciently, etc.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wolf</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1826/</guid></item><item><title>Adding multiple users to group doesn't work</title><link>https://forge-allura.apache.org/p/allura/tickets/1808/</link><description>If I try to add multiple users to a group at once, only the last one adds.  Also, if any one of them are not found, they all fail with "User [u'user04', u'user3535'] not found"</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1808/</guid></item><item><title>Skip ad calls for certain projects</title><link>https://forge-allura.apache.org/p/allura/tickets/1800/</link><description>Along the same lines of [#1795] but for a list of specified projects, omit all ad calls on all their pages.

No UI needed to maintain projects.  Can be in global_settings collection, and updated by hand.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1800/</guid></item><item><title>Move wiki right sidebar data to the top [18407]</title><link>https://forge-allura.apache.org/p/allura/tickets/1798/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/18407

----

Hi,

    https://sourceforge.net/p/scipad/wiki/Tested%20on/

There seem to be an invisible limit in the width that a wiki page can support.

The preview of my page (when modifying it) is OK (try Edit, then Preview). But after saving, the page is truncated down to a far too small width which is independent of the screen or browser window width, therefore truncating content like tables far too early.

Note that this seems to be quite general:

    https://sourceforge.net/p/scipad/home/

shows snapshots that are now truncated (whereas they were not at the beginning of my SF2.0 project).

----</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1798/</guid></item><item><title>There should be artifacts comments preview</title><link>https://forge-allura.apache.org/p/allura/tickets/1769/</link><description>We provide preview support when editing main textual body of an artifact (ticket details, wiki content, etc.), but not when editing comments to an artifacts. Apparently, for consistency, we should allow to do that, otherwise we get markup underuse (because people are afraid to use it, not knowing if it'll come ok or no), or get broken markup.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Sokolovsky</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1769/</guid></item><item><title>Use GA Custom Fields to track "tool" activity on Allura tools</title><link>https://forge-allura.apache.org/p/allura/tickets/1625/</link><description>Allura pages should set a custom field in GA indicating the "tool:$toolname" in the page scope so that we can track how many tracker page views vs wiki page views there are over time. </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1625/</guid></item><item><title>Write up blog posts on HTML5/CSS3 improvements</title><link>https://forge-allura.apache.org/p/allura/tickets/1578/</link><description>* Web fonts
* Sass/Compass
* Performance improvements

https://engr.geek.net/jira/browse/AT-776</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1578/</guid></item><item><title>Make discussion thread list sort by date of last post</title><link>https://forge-allura.apache.org/p/allura/tickets/1565/</link><description>Currently, thread list is sorted by mod_date of internal thread object. mod_date is updated on some administrative actions, like thread moderation, so thread order may change unexpectedly to users. This was discussed on the mailing list and it was decided that it's worth to add "last post date" field to a thread object and sort based on that.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Sokolovsky</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1565/</guid></item><item><title>Allow ctrl/middle - click on ticket rows</title><link>https://forge-allura.apache.org/p/allura/tickets/1490/</link><description>Currently they change the current page, instead of opening a new tab.  Implementation suggestion: http://horia.me/the-middle-click</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1490/</guid></item><item><title>Switch to jquery.elastic.js for autogrowing textareas</title><link>https://forge-allura.apache.org/p/allura/tickets/1489/</link><description>jquery.elastic.js has two main advantages over our current plugin: it doesn't collapse the textarea down to one row and it seems to be a little gentler on CPUs. Under the covers elastic relies more on jQuery methods to calculate the new height, vs. exptextarea's homebrew height calculation. Consequently elastic is better positioned to benefit from ongoing jQuery optimizations.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kyle Adams</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1489/</guid></item><item><title>Markdown Syntax Guide should give both syntax and rendition</title><link>https://forge-allura.apache.org/p/allura/tickets/1480/</link><description>https://sourceforge.net/p/allura/tickets/markdown_syntax

Currently, markdown guide gives just syntax examples in plain text, so you need to read it when you just want to look up needed feature, and it's boring. Would be nice to have both syntax examples and renditions.

Other issue is that formatting may use some cleanup - currently, descriptive text sometimes is rendered as normal text, sometimes as &lt;pre&gt;. Probably makes sense to use &lt;pre&gt; just for syntax examples - another measure to help with quick lookup.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Sokolovsky</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1480/</guid></item><item><title>Make the project name in the header vertically centered with the project icon</title><link>https://forge-allura.apache.org/p/allura/tickets/1455/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dean Henrichsmeyer</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1455/</guid></item></channel></rss>