<?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:"p2"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:57 -0000</lastBuildDate><item><title> All project help pages were lost when migrating MediaWiki [ss7733]</title><link>https://forge-allura.apache.org/p/allura/tickets/7435/</link><description>[forge:site-support:#7733]

&gt;The Lynkeos application help is currently hosted in the MediaWiki of the Lynkeos project at https://sourceforge.net/apps/mediawiki/lynkeos/index.php?title=Help:Contents.
I followed the guide http://sourceforge.net/p/forge/documentation/SourceForge%20MediaWiki%20Importer/ to migrate the MediaWiki.
The new Wiki at https://sourceforge.net/p/lynkeos/wiki/Main_Page/ does contain some pages of the original MediaWiki, but none of the Help pages are present.

Did a test import here: https://sourceforge.net/p/strawhat/lynkeos-mw/

From what I can see, I don't see a reason *not* to import the "help:" namespace.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Fri, 06 Mar 2015 12:19:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7435/</guid></item><item><title>"list index out of range" error on git _iter_commits_with_refs</title><link>https://forge-allura.apache.org/p/allura/tickets/6629/</link><description>This was introduced in [#5775]

~~~~
File '/var/local/allura/Allura/allura/templates/widgets/repo/tree_widget.html', line 21 in top-level template code
  {% set ls = list(tree.ls()) %}
File '/var/local/allura/Allura/allura/model/repo.py', line 532 in ls
  last_commit = LastCommit.get(self, create=False)
File '/var/local/allura/Allura/allura/model/repo.py', line 813 in get
  last_commit_id = cls._last_commit_id(tree.commit, path)
File '/var/local/allura/Allura/allura/model/repo.py', line 787 in _last_commit_id
  rev = commit.repo.log(commit._id, path, id_only=True).next()
File '/var/local/allura/ForgeGit/forgegit/model/git_repo.py', line 307 in log
  for ci, refs, renamed in self._iter_commits_with_refs(*args):
File '/var/local/allura/ForgeGit/forgegit/model/git_repo.py', line 393 in _iter_commits_with_refs
  name_stat_parts = commit_lines[1].split(' ')
IndexError: list index out of range
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:20 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6629/</guid></item><item><title>Allura tickets system intermittently discards replies to comments [ss4454]</title><link>https://forge-allura.apache.org/p/allura/tickets/6381/</link><description>Ref: [allura:tickets:#4454]

keithmarshall:
&gt;&gt;&gt;Within the browser view of a ticket, I'll select the "reply" option in one of the follow-up comment panes. I'll enter my reply, in the input pane which is presented. When I subsequently select the "post reply" option, it's a complete lottery as to whether the reply will actually be posted; all too frequently, the system records an edit to the original message, (in which I've changed nothing), while dropping the actual reply on the floor, whence it vanishes into oblivion.

&gt;&gt;&gt;This is happening way too often; it is becoming increasingly frustrating.

me:
&gt;&gt;Can you provide a time frame for when this has been occurring (we've been working through some site issues the past few days which I could see as related) and some specific examples that we can check the logs for?

&gt;&gt;Also, as a personal recommendation, I've been using the Lazarus browser plugin (for FF and Chrome), and helped me recover lost text on many occasions.

keithmarshall:
&gt;I've noticed it intermittently, over several months; pretty much, ever since MinGW migrated to the Allura platform. Most recent occurrence was today, (just a short while before I raised this issue itself), when I attempted to add the side issue references on https://sourceforge.net/p/mingw/bugs/1989/

&gt;I experienced a similar issue yesterday, on https://sourceforge.net/p/mingw/bugs/1973/ (I think); tracking down any earlier occurrences may be too difficult to contemplate, but there have been several.

&gt;Thanks for the Lazarus pointer; I'll certainly look into it. However, I've simply gotten into the habit of using Ctrl-A Ctrl-C in the input pane, just prior to selecting "post reply".

&gt;One further point, which may or may not be related: sometimes, when a reply is successfully posted, it becomes divorced from its parent, and presented as an apparent top level discussion item, (usually with an intervening "page break").

So we don't need to do a lot of timestamp comparing to figure out which reply specifically, it looks like it's this one: https://sourceforge.net/p/mingw/bugs/1989/#3e85/cd7b/d222/aba9/76e9</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:10 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6381/</guid></item><item><title>RSS syndication not formatting right</title><link>https://forge-allura.apache.org/p/allura/tickets/6230/</link><description>See https://sourceforge.net/p/lportal/news/ for example - blog posts pulled from elsewhere via RSS are displaying as raw HTML.

If you check the Markdown on the blog posts directly, it looks like the html is being escaped during import. eg. The Markdown on [this post](https://sourceforge.net/p/lportal/news/2013/05/5-astuces-pour-am%C3%A9liorer-lusage-de-la-console-de-script-de-liferay/), starts with:

~~~~
&amp;lt;p&amp;gt;
&amp;lt;em&amp;gt;// La version fran&amp;amp;ccedil;aise de cet article est l&amp;amp;agrave; : &amp;lt;a href="http://www.liferay.com/web/sebastien.lemarchand/blog/-/blogs/5-astuces-pour-ameliorer-l%E2%80%99usage-de-la-console-de-script-de-liferay"&amp;gt;5 astuces pour am&amp;amp;eacute;liorer l&amp;amp;rsquo;usage de la console de script de Liferay&amp;lt;/a&amp;gt;.&amp;lt;/em&amp;gt;&amp;lt;/p&amp;gt;
&amp;lt;p&amp;gt;
&amp;lt;em style="line-height: 1.5;"&amp;gt;&amp;lt;span style="line-height: 1.5;"&amp;gt;// If you use a RSS reader to read this post, please switch to the HTML page to correctly view the code snippets.&amp;lt;/span&amp;gt;&amp;lt;/em&amp;gt;&amp;lt;/p&amp;gt;
&amp;lt;p&amp;gt;
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rich Bowen</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6230/</guid></item><item><title>test upgrade for scummvm [ss3006]</title><link>https://forge-allura.apache.org/p/allura/tickets/5916/</link><description>[forge:site-support:#3006]

&gt;On IRC, ctsai suggested a test migration of the ScummVM project to Allura in a sandbox for evaluation purposes to catch problems as soon as possible. We (myself and a few other devs) think that would be great to try.

They previously tried to upgrade and then asked for a revert.

For reference, in addition to problems with importing their very large svn repo (which should be fixed now with svn hotcopy), they also noted these issues: http://usecode.org/misc/tracker.txt</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/5916/</guid></item><item><title>Command for fixing discussion instances in trackers with moved tickets</title><link>https://forge-allura.apache.org/p/allura/tickets/5727/</link><description>Write a paster command to fix discussions for trackers messed up by buggy 'ticket move' feature.

The bug in 'ticket move' feature was fixed in [#5691], [#5708]. Command should fix the existing issues caused by that bug.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Igor Bondarenko</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/5727/</guid></item><item><title>Ticket creator shouldn't have elevated write on Private tickets [ss2513]</title><link>https://forge-allura.apache.org/p/allura/tickets/5647/</link><description>[forge:site-support:#2513]

When a ticket is marked private, the ticket creator still has update privileges even if they shouldn't according to the ticket tool's permissions.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/5647/</guid></item><item><title>on some filesystems, error when deleting SVN r1 working copy dir</title><link>https://forge-allura.apache.org/p/allura/tickets/5508/</link><description>SVN creates a temp dir to do an initial r1 commit.  For some reason (maybe when upgraded to svn 1.7) a file handle is left open, and then the rmtree() for that working dir fails if the filesystem is on FUSE or NFS.  Making this a configurable directory (default /tmp) should avoid that and let the delete succeed despite the file.</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/5508/</guid></item><item><title>Not all tools showing as installed on Admin -&gt; Tools</title><link>https://forge-allura.apache.org/p/allura/tickets/5193/</link><description>eg. https://sourceforge.net/p/allura/admin/tools

Not all the tools are showing as installed at the bottom, though the tools themselves appear to be working fine. As such, without knowing the exact URLs, users can't access the tool options/permissions/etc., and there's no way to re-arrange them.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/5193/</guid></item><item><title>svn hooks need conversion</title><link>https://forge-allura.apache.org/p/allura/tickets/5076/</link><description>Due to differences in server configs, migrated svn hooks don't seem to work.

Errors with pre-commit hooks can cause commits to get blocked, ref: [forge:site-support:#874]

&gt;after upgrading the megameklab project, we can't checking anything into SVN now. We get the following error:
/svn/p/megameklab/code/hooks/pre-commit: line 3: /var/local/mastertree/host/sfp-svn/hook-scripts/check-case-insensitive.py: No such file or directory

I imagine other hooks would fail similarly. We should probably also remove any unnecessary hooks and update the data on other hooks. For example, the user in [forge:site-support:#862] had the following:

~~~~
-bash-3.2$ pwd
/home/svn/p/callflow/code/hooks


-bash-3.2$ cat post-commit     
#!/bin/bash
# The following is required for site integration, do not remove/modify.
# Place user hook code in post-commit-user and it will be called from here.
curl -s http://sourceforge.net/auth/refresh_repo/p/callflow/code/

DIR="$(dirname "${BASH_SOURCE[0]}")"
if [ -x $DIR/post-commit-user ]; then  exec $DIR/post-commit-user "$@"


-bash-3.2$ cat post-commit-user 
#!/bin/sh
# THIS FILE IS AUTOGENERATED - DO NOT EDIT
/var/local/mastertree/host/sfp-svn/hook-scripts/sf-svn-stats-hook.py $*
/var/local/mastertree/host/sfp-svn/hook-scripts/keepsake -p "$1"
/var/local/mastertree/host/sfp-svn/hook-scripts/svnnotify --repos-path "$1" --revision "$2" --to "callflow-svn@lists.sourceforge.net" --subject-prefix "SF.net SVN: callflow:" --subject-cx --no-first-line --with-diff --viewcvs-url "http://callflow.svn.sourceforge.net/callflow/?rev=%s&amp;view=rev" --user-domain "users.sourceforge.net" --footer "This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site." -l /usr/bin/svnlook --max-diff-length 100000
exit 0
~~~~

 * We should probably first remove the "AUTOGENERATED" link, since that's no longer true.

 * I think we can probably just remove the sf classic specific hooks (`sf-svn-stats-hook.py` and `keepsake`).

 * For svnnotify, we should fix the path (iirc, it's in the standard location `/usr/bin/svnnotify/` though just `svnnotify` works), and update the url to the code browser (ie., the `--viewcvs-url` option)


We have a few other pre-configured hooks users can add, but we didn't allow custom hooks for svn repos on classic, so it should be a finite list.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/5076/</guid></item><item><title>View revisions for a file/dir</title><link>https://forge-allura.apache.org/p/allura/tickets/5037/</link><description>Currently all the 'History' links in the SCM browse go to a URL like https://sourceforge.net/p/allura/git/ci/0298d85091dd970b0c6d57c914e43643b604a6a8/log/ which shows the revisions starting at the given commit.  There should be a way to view revisions limited to a specified directory or file.  E.g. URL might be something like https://sourceforge.net/p/allura/git/ci/0298d85091dd970b0c6d57c914e43643b604a6a8/log/ForgeBlog/forgeblog/tests/  This needs to be implemented for Git, Hg, and SVN.

Then, change the History links so that when you're browsing a tree or file, the link goes to the /log/ URL containing the file/folder path.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/5037/</guid></item><item><title>post-receive-user incorrectly created when cloning a repo</title><link>https://forge-allura.apache.org/p/allura/tickets/5022/</link><description>When forking a repo within Allura, the post-receive-user file should not be created.  Currently it is created like the following, which is self-recursive and bad.

~~~~
#!/bin/bash
# The following is required for site integration, do not remove/modify.
# Place user hook code in post-receive-user and it will be called from here.
curl -s http://sourceforge.net/auth/refresh_repo/p/simplemvcv/code/

DIR="$(dirname "${BASH_SOURCE[0]}")"
if [ -x $DIR/post-receive-user ]; then  exec $DIR/post-receive-user
fi
~~~~</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/5022/</guid></item><item><title>Forum notifications not working [ss728]</title><link>https://forge-allura.apache.org/p/allura/tickets/4994/</link><description>[forge:site-support:#728]

&gt; After the Sourceforge upgrade of the SymmetricDS project (https://sourceforge.net/p/symmetricds/discussion/), the ability to subscribe to posts was lost. Current subscriptions stopped working and the Subscribe button doesn't seem to do anything. Is there a fix avaiable?

and

&gt;Yeah, since our upgrade of the SymmetricDS project, around 9/13/2012, emails are not being received when new topics are posted to our forums. We've tried combinations of "subscribing" and "unsubscribing" to the individual forums, but no combination seems to work.

&gt;Prior to the upgrade, we reliably received email notifications whenever a post was replied to or a new post was created (assuming you weren't the one replying yourself). We have tried to various email addresses as well, so we don't think it's somehow spam-filter related.

&gt;Thanks!</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/4994/</guid></item><item><title>SVN repo import of old 'adtools' repository fails in allura [ss723]</title><link>https://forge-allura.apache.org/p/allura/tickets/4991/</link><description>[forge:site-support:#723]

&gt;When issuing a SVN repository import in the new Allura site of the "adtools" project, the import continuously fails. It failed first with the initial project upgrade and then also with a second manual SVN repo reimport from the classic repository @ sf.net.

I tried importing https://adtools.svn.sourceforge.net/svnroot/adtools as well and it consistently fails for me.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4991/</guid></item><item><title>Need good UI for dozens of same tool types [ss617]</title><link>https://forge-allura.apache.org/p/allura/tickets/4957/</link><description>[forge:site-support:#617]

&gt;Hi,

&gt;since switching to Allura, all our mercurial sub-repositories (about 20) are shown in the head of our project page, which is absolutely confusing.

&gt;Mercurial is able store the sub-repositories in parallel to the base repository, which we had to do in the old system. So I tried to fix the problems above, by moving the sub-repositories into the main repository using the shell service. But I have no permissions any more, since all directories in /home/hg/p/bina are owned by root.

&gt;During our project upgrade, there was also a shell script "create-repo.sh" laying around in the same directory, which we used for creating new mercurial sub-repositories. This script was erroneously converted to a new mercurial repository (create-repo-sh) and should be deleted again.

&gt;Please, fix these problems or downgrade our project back, until the mercurial problems have been resolved.

&gt;Thanks,

&gt;Andreas

I've rolled back the project until we can figure out how to deal with this mercurial setup.</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/4957/</guid></item><item><title>svn code browser showing inconsistent data [ss542]</title><link>https://forge-allura.apache.org/p/allura/tickets/4935/</link><description>[forge:site-support:#542]

&gt;In SF1, the SCM code viewer (viewvc) showed me the rev, age, and log message for the last commit made in the tree under that directory. So you could easily explore down the tree to find the last commit, for example.

&gt;In SF2, I cannot figure out what the new Subversion code browser is showing me for directories. It shows a date and commit info (rev and log message), but it is not the most recent in the tree under that. And it seems to change from time to time (without any commits). Yesterday I was seeing almost-newest commit info. Today I seem to be seeing the very first commit under that tree.

&gt;See also [allura:tickets:#4728], [forge:site-support:#228] and [allura:tickets:#4754]. If I'm reading it right, you had a similar problem with Mercurial (all_commit_ids), which was fixed, perhaps only for that SCM system?

For example, [rev 1407](/p/phplot/code/1407/) of their repo includes `/branches/Rel6/phplot/phplot.php` but viewing the directory that contains it in the code browser, it currently shows rev 1396. Screenshot attached.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4935/</guid></item><item><title>check mime type for text/binary for code browser [ss539]</title><link>https://forge-allura.apache.org/p/allura/tickets/4933/</link><description>[forge:site-support:#539]

&gt;Trying to browse Subversion repository, for example page

&gt;https://sourceforge.net/p/gputils/code/813/

&gt;for every file you'll see "Cannot display: file marked as a binary type."

&gt;I do not see any mark of binary type.

&gt;The files have properties:

~~~~
Properties on 'ChangeLog':
  svn:keywords
    Author Date Id Revision
  svn:eol-style
    native
~~~~

&gt;The svn-book says "If the file has no svn:mime-type property, or has a MIME type that is textual (e.g., text/*), Subversion assumes it is text. Otherwise, Subversion assumes the file is binary."

&gt;These files have no svn:mime-type property, so they are assumed to be text by subversion.</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/4933/</guid></item><item><title>dosbox svn repo displaying "no files" [ss473]</title><link>https://forge-allura.apache.org/p/allura/tickets/4886/</link><description>[forge:site-support:#473]

https://sourceforge.net/p/dosbox/code-0/3797/tree/

I can get a checkout just fine, so as far as I can tell, the repo itself is working properly, but dosbox's svn repo browser shows "-- no files --" for rev 3791 and newer (at time of writing, rev 3797 is the latest).

Possibly related, when I first checked it, it seemed to be stuck "analyzing" so I gave it a manual refresh (just a regular one, not a clean refresh, I can't do those). The subsequent analysis finished, but now we're in this state.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4886/</guid></item><item><title>permission inconsistency on certain subprojects [ss331]</title><link>https://forge-allura.apache.org/p/allura/tickets/4862/</link><description>[forge:site-support:#331]

Despite permissions that appear fine to me, http://sourceforge.net/p/bexis/portablebexis/tickets/ doesn't show anything except to those with admin privileges. More detail in the support ticket.</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/4862/</guid></item><item><title>Add missing instrumentation for commit view pages</title><link>https://forge-allura.apache.org/p/allura/tickets/4832/</link><description>`{"time": "2012-08-30 17:28:07,525", "level": "INFO ", "name": "stats", "message": {"url": "/p/slashmobdeploy/code/ci/6cac017cf4e182af52aa5af6853c16946876184b/", "uptime": 2710, "request_category": "git", "timings": {"total": 94767, "markdown": 1, "ming": 137, "jinja": 293, "mongo": 39}}}`

This page takes a terribly long total time to render, but none of the individual timings are very high.  We should have more instrumented functions to help identify what is taking so long.</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/4832/</guid></item><item><title>'send_simple' AttributeError when saving a ticket [ss252]</title><link>https://forge-allura.apache.org/p/allura/tickets/4737/</link><description>~~~~
Module allura.model.discuss:183 in add_post
&lt;&lt;      def add_post(self, **kw):
               """Helper function to avoid code duplication."""
               p = self.post(**kw)
               p.commit()
               self.num_replies += 1
&gt;&gt;  p = self.post(**kw)
Module allura.model.discuss:217 in post
&lt;&lt;              log.info('Auto-approving message from %s', c.user.username)
                   file_info = kw.get('file_info', None)
                   post.approve(file_info)
               else:
                   self.notify_moderators(post)
&gt;&gt;  post.approve(file_info)
Module allura.model.discuss:528 in approve
&lt;&lt;                  self.acl, author.project_role()._id, 'unmoderated_post')
               g.post_event('discussion.new_post', self.thread_id, self._id)
               self.notify(file_info=file_info)
               artifact = self.thread.artifact or self.thread
               session(self).flush()
&gt;&gt;  self.notify(file_info=file_info)
Module allura.model.discuss:552 in notify
&lt;&lt;              if hasattr(artifact, 'notify_post'):
                       if artifact.notify_post:
                           n.send_simple(artifact.monitoring_email)
                   else:  # Send if no extra checks required
                       n.send_simple(artifact.monitoring_email)
&gt;&gt;  n.send_simple(artifact.monitoring_email)
AttributeError: 'NoneType' object has no attribute 'send_simple'
~~~~</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/4737/</guid></item><item><title>maintaining previous comment text when editing ticket fields</title><link>https://forge-allura.apache.org/p/allura/tickets/4530/</link><description>I've run into this case a few times already where I'll start to write a comment on a ticket, then after I'm done, I realize I want to edit the ticket fields as well, so I click the edit icon, only to find the reply I had typed out is now gone. Doesn't affect me personally too much, because [Lazarus](http://getlazarus.com/), but I can see this becoming very frustrating for users.

So, in short, I think if you have text in the reply box before you click the edit button on a ticket, that text should be transferred to the new reply box.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/4530/</guid></item><item><title>ticket search breaking on certain characters [25347]</title><link>https://forge-allura.apache.org/p/allura/tickets/4111/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/25347

&gt;Hello,

&gt;I've added a custom search: labels:Modèle
And I have no more left menu when I go to the ticket list of my project
When I go to the admin panel and try to edit searches, I got an error 500 so I can't remove it.

&gt;With the search input on the ticket list, if I try "labels:entité", the list is correctly filtered, but when I try "labels:modèle", I also got an error 500.

&gt;I think the "modèle" keyword is buggy

I tried adding the same label to one of my test projects and found the same thing.</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/4111/</guid></item><item><title>Users need a way to backup allura data [idt 824] NEEDS INI</title><link>https://forge-allura.apache.org/p/allura/tickets/3154/</link><description>https://sourceforge.net/apps/ideatorrent/sourceforge/ideatorrent/idea/824/

&gt;SF clearly says that the backup of the project data is left to project admins:

&gt;https://sourceforge.net/apps/trac/sourceforge/wiki/Backup%20your%20data

&gt;Fine.

&gt;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)?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:20 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3154/</guid></item></channel></rss>