<?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 labels:"bitesize" AND status:open</description><language>en</language><lastBuildDate>Fri, 08 Feb 2019 15:21:52 -0000</lastBuildDate><item><title>Update export API docs &amp; script for with_attachments</title><link>https://forge-allura.apache.org/p/allura/tickets/8064/</link><description>The `with_attachments` param added in [#8052] should be added to `api.raml`.  Also `allura/scripts/project_export` should be updated to have that as a script option.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 17 Mar 2016 15:23:05 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8064/</guid></item><item><title>Improvements to AlluraTimerMiddleware</title><link>https://forge-allura.apache.org/p/allura/tickets/7977/</link><description>It'd be useful to have AlluraTimerMiddleware wrap the project nav logic.  This would help identify any issues related to that (e.g. project with tons of tools)

And the first "ming" timer should be renamed "ming-iter" so that the high call counts it produces is separate from the regular ming counts.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Fri, 08 Feb 2019 15:21:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7977/</guid></item><item><title>misleading link to wrong rss file</title><link>https://forge-allura.apache.org/p/allura/tickets/7860/</link><description>This is issue was reported in the IRC support channel this is a summary from both Support channel and sog-eng channel, please see the attachment for full support channel transcripts:

this is the user's profile that reported the bug: https://sourceforge.net/u/cprecup/profile/

----

Reported issue:
The bug is community members can see the old content via the RSS feed icon which is unexpected.

----

From Support Channel:
cprecup
I am having an issue with my profile displayed information on sourceforge.net: my activity (old though) is not being displayed anywhere. I can only find it by going to the specific project and searching for my username. Isn't there a way to fix this?

Project link: https://sourceforge.net/projects/brlcad/, Search results: https://sourceforge.net/p/brlcad/mailman/search/?q=cprecup. If you click on my profile page on the "feed" icon, it will still show my latest (but old) contributions in an xml format

----
Example of issue:

https://sourceforge.net/u/cprecup/profile/feed.rss has content, but https://sourceforge.net/u/cprecup/activity/?page=0&amp;limit=100 is empty.

The "User Activity" side-bar on the /u/cprecup/profile/
profile/feed.rss is different from …/profile/activity/feed.rss

Its misleading that the RSS icon above the "User Activity" side-bar goes to …/profile/feed.rss

----

Currently there are no plans to import /profile/feed.rss data into /profile/activity/
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Barrett</dc:creator><pubDate>Thu, 17 Mar 2016 15:21:13 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7860/</guid></item><item><title>(Re-)add appropriate links to Markdown Syntax guide</title><link>https://forge-allura.apache.org/p/allura/tickets/7169/</link><description>In the Markdown Syntax Guide (ie., the "Formatting Help" link in the left sidebar), we used to include links to http://daringfireball.net/projects/markdown/syntax to provide more detail for users wanting to go beyond the basic formatting.

This was (probably unintentionally) removed in the following commit: https://forge-allura.apache.org/p/allura/git/ci/ad07922261c339cc24555587a38113c5fc2fb421

Hence, this should be added back. We should also consider adding links to the python library we use if/where appropriate.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Mon, 15 Oct 2018 09:40:02 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7169/</guid></item><item><title>Metadata events</title><link>https://forge-allura.apache.org/p/allura/tickets/6997/</link><description>Create events for:

* new project
* add member to project
* add screenshots
* update project categories, description, etc (don't want to get too detailed, probably)
* user profile changes</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 31 Mar 2015 10:11:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6997/</guid></item><item><title>Include bulk_export_download_instructions in export API result</title><link>https://forge-allura.apache.org/p/allura/tickets/6920/</link><description>The `bulk_export_download_instructions` text that is included in emails after an export should also be included in the success API result for a bulk export.  Then users of the API will have instructions handy and not have to do a manual export to get them via email.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Sun, 29 Mar 2015 18:10:16 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6920/</guid></item><item><title>Export API's tools params should be optional</title><link>https://forge-allura.apache.org/p/allura/tickets/6919/</link><description>Make the Tools parameter when scheduling an export job optional and export all existing when it is missing, otherwise the backup Script needs to be changed every time a tool is added and manual things to do usually are forgotten regularly.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 30 Jun 2014 20:33:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6919/</guid></item><item><title>When previewing a comment, "cancel" doesn't visibly clear input [ss5771]</title><link>https://forge-allura.apache.org/p/allura/tickets/6816/</link><description>[forge:site-support:#5771]

&gt;the cancel button in a bug ticket when in preview mode doesn't cancel. not sure about the other buttons either, they also map to #

It looks like it *does* actually clear the input, but that's not visible until you click the "EDIT" button.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Tue, 31 Mar 2015 19:57:01 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6816/</guid></item><item><title>Need a minimum start date for forum stats</title><link>https://forge-allura.apache.org/p/allura/tickets/6664/</link><description>The forum stats widget doesn't have a minimum start date which means:

1. the "All Dates Before" feature just doesn't work
2. a really old date (back to 1900-01-01 it seems) can be used with just a long segment at the beginning of 0 stats.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Fri, 30 Jan 2015 22:21:11 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6664/</guid></item><item><title>New ticket label tags are a bit bulky / unpretty</title><link>https://forge-allura.apache.org/p/allura/tickets/6018/</link><description>The new tag library used to manage ticket labels don't look as nice as the previous library.  Reducing the padding and maybe rounding the corners a bit more would probably help.  Maybe even adding a faint gradient (or not; I'm a programmer, not a designer).

Also, the tags render to the left of the input, moving the input box.  It would be better to render them to the right so that the input doesn't move.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cory Johns</dc:creator><pubDate>Thu, 30 Oct 2014 08:21:46 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6018/</guid></item><item><title>hovering over edit date should display exact edit time [ss3211]</title><link>https://forge-allura.apache.org/p/allura/tickets/6008/</link><description>[forge:site-support:#3211]

&gt;One problem is that the forum software currently allows a message to be edited after someone replied to it. The exact edit and reply dates not being shown can cause confusion for those who read the thread at a later time because both dates become identical ("5 days ago" for 2 messages posted in the same day). Example: https://sourceforge.net/p/advtor/discussion/2254385/thread/efc91b72/ - after the error from a posted screenshot was corrected and a reply was given to that post, the screenshot was replaced with another one showing another error.

Hovering over the comment date will show the exact time, but hovering over the last edit date does not. Can cause confusion.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Sat, 03 Jan 2015 16:52:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6008/</guid></item><item><title>when editing the view columns in tracker results, sorting on a field column re-adds hidden columns</title><link>https://forge-allura.apache.org/p/allura/tickets/3475/</link><description>view any tracker search result
click the column editor, hide a column or two
click a remaining column header to sort
hidden columns re-appear</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Hoffman</dc:creator><pubDate>Thu, 17 Mar 2016 15:22:30 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3475/</guid></item><item><title>Tags sorted in random way. Mercurial code browser [22807]</title><link>https://forge-allura.apache.org/p/allura/tickets/3286/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/22807

&gt; Visit:

&gt;    https://sourceforge.net/p/jdone/code/?branch=ref%2Fdefault 

&gt;and you see:

&gt;Tags

&gt;&gt; t0.2 66
 t0.3 78
 t0.1 23
 tip 80

&gt;**t0.3** below **t0.2**!

&gt;I expect that tats was sorted reverse chronological (most recent on top).

If that's not it, can you explain the sorting method?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Mon, 09 Feb 2015 00:42:50 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3286/</guid></item></channel></rss>