<?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:"ux"</description><language>en</language><lastBuildDate>Thu, 20 Jun 2019 12:48:35 -0000</lastBuildDate><item><title>Cannot resize ticket display</title><link>https://forge-allura.apache.org/p/allura/tickets/8310/</link><description>As the subject says</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sebb</dc:creator><pubDate>Thu, 20 Jun 2019 12:48:35 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8310/</guid></item><item><title>Ticket list does may fail to display full label titles</title><link>https://forge-allura.apache.org/p/allura/tickets/8309/</link><description>The list of tickets can be sorted by various columns. When the sort is done A-&gt;Z, entries with missing values come first (as is to be expected). However this can result in the column label partially disappearing, as the column width appears to be determined purely by the values. The minimum column width should be set large enough to display the label.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Sebb</dc:creator><pubDate>Thu, 20 Jun 2019 12:43:38 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8309/</guid></item><item><title>Project Categorization select and button are attached together</title><link>https://forge-allura.apache.org/p/allura/tickets/8247/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:22 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8247/</guid></item><item><title>Improve admin categorization page</title><link>https://forge-allura.apache.org/p/allura/tickets/8135/</link><description>* Remove duplication of prefix e.g. "License ::" on every drop down
* hide labels, since we don't really use
* have smart recommendations for OS and License
* autocomplete search</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Fri, 11 Nov 2016 15:31:59 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8135/</guid></item><item><title>Improve project creation UX</title><link>https://forge-allura.apache.org/p/allura/tickets/8094/</link><description>Things like:

* better UX when login is required, to create a project (instead of simply a login page)
    * use login overlay (like project *import* does)
    * or, login page could support showing a "reason" message on it
* get rid of lag on name suggestions</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 05 Jul 2016 17:44:39 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8094/</guid></item><item><title>Don't duplicate titles on neighborhood pages</title><link>https://forge-allura.apache.org/p/allura/tickets/8046/</link><description>When on neighborhood level pages like a wiki, the project and neighborhood name are both displayed but they are the same and it looks weird, especially if they run into each other.  We should omit one on pages of that type.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Fri, 05 Feb 2016 19:36:12 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8046/</guid></item><item><title>Change "Label" admin option to "Rename"</title><link>https://forge-allura.apache.org/p/allura/tickets/8037/</link><description>I think the "Label" admin option would be easier to understand if it was "Rename".

This may show up in several places in the UI, and we should update all of them.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 25 Jan 2016 15:34:14 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8037/</guid></item><item><title>Update modal css (simple-flat-dark)</title><link>https://forge-allura.apache.org/p/allura/tickets/8036/</link><description>To coincide with the release of our new toolbar, we should give the lightbox modals a slightly newer look.

A dark, simple look would go a long way in improving our option’s aesthetic.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 25 Jan 2016 15:34:19 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8036/</guid></item><item><title>Use Allura icon in favicon, footer, etc</title><link>https://forge-allura.apache.org/p/allura/tickets/8017/</link><description>We should use the Allura icon in more places like the favicon (existing favicon.ico file is a gzipped turbegears logo, and isn't referenced) and in the footer by our name.  Can copy from sf.net styling of that footer spot.  Maybe show the logo on the homepage or a default sitewide logo too?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 25 Jan 2016 16:40:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8017/</guid></item><item><title>Dialog 'cancel' link in wrong place</title><link>https://forge-allura.apache.org/p/allura/tickets/8016/</link><description>On dialog boxes like new tool installation, and "Checkout URL" repo options, the 'cancel' link is in the wrong place.  Perhaps related to recent icon changes including that "close" link in upper right of those dialogs.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 30 Nov 2015 15:35:24 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8016/</guid></item><item><title>Remove tool icons from project nav</title><link>https://forge-allura.apache.org/p/allura/tickets/8004/</link><description>Per discussion at thread http://mail-archives.apache.org/mod_mbox/allura-dev/201510.mbox/%3CCAOH-DerrdKor_BdfecYXoF0sfiZ%3DK893%3DzmQiet%2B%2Bc_-8vMUSw%40mail.gmail.com%3E</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 02 Nov 2015 15:09:14 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8004/</guid></item><item><title>Adding attachment to wiki loses your text changes</title><link>https://forge-allura.apache.org/p/allura/tickets/7998/</link><description>When editing a wiki page and adding or removing an attachment, any changes you may have made to the wiki text get lost.

I'd suggest we make the add &amp; delete attachments into ajax calls.  (Another option would be submit the wiki text form too and controller would handle both types of changes at once).  Ajax would be a nice direction towards someday allowing drag/drop of images into a markdown editor and auto-attach and insert `[[img src=...]]` for you.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 11 Jan 2016 15:26:30 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7998/</guid></item><item><title>Fix layout at bottom of subscriptions page</title><link>https://forge-allura.apache.org/p/allura/tickets/7984/</link><description>`/auth/subscriptions` has a bad layout under the table.  It'd be better to have "Email Format" and the dropdown adjacent to each other on the same line.  And then align the "Save" button to the far right, also on the same line.

A few other relatively easy cleanup tasks would be:

* remove Topic, Type, and Frequency columns, since they aren't used
* rename App to Tool
* provide a way for apps to indicate they don't have any notifications (search, admin, activity, etc) and skip the rows for those types of apps</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 19 Oct 2015 13:54:46 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7984/</guid></item><item><title>In editor, pasting should be auto-wrapped</title><link>https://forge-allura.apache.org/p/allura/tickets/7983/</link><description>When pasting a large chunk of text into the markdown editor, it often would be useful to automatically wrap it with `~~~~` or indent it.  People who paste code snippets or log lines would benefit from this, especially if they are not familiar with markdown and don't realize it needs to be in a code block to avoid `__foo__` from getting formatted etc.  I think this would help alleviate problems expressed in https://sourceforge.net/p/forge/feature-requests/134/

However, that won't be appropriate all the time, since some people could paste large amounts of regular text or even markdown formatting (e.g. restructuring a wiki page).  Turning it into a code block won't be helpful.  We'll need some sort of UI to make this work well.  I am thinking that we show a notification after it happens, and tell the user how they can click the code snippet button to undo it.  We can also save a cookie/sessionStorage setting to not do it again. 

Here's an autoindent snippet proof-of-concept:

~~~~
cm = editor.codemirror;

// based on https://github.com/codemirror/CodeMirror/issues/2120
cm.on("change", function(cm, change) {
  if (change.origin != "paste" || change.text.length &lt; 2) {
    return;
  }
  var spaces = cm.options.tabSize;
  cm.operation(function() {
    for (var line = change.from.line, end = CodeMirror.changeEnd(change).line; line &lt;= end; ++line) {
      cm.indentLine(line, spaces);
    }
  });
});
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Fri, 04 Sep 2015 14:24:45 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7983/</guid></item><item><title>Editor should autocomplete artifact references and macros</title><link>https://forge-allura.apache.org/p/allura/tickets/7982/</link><description>In the markdown editor, it would be great if you type `[` it shows a list of artifact choices. And if you type `[[` it shows a list of macro choices.  Using the autocomplete addon for codemirror can get us a lot of the way there.  https://codemirror.net/doc/manual.html#addon_show-hint

We probably will want to save recently visited tickets, wiki pages, and other artifacts in the browser's localStorage or sessionStorage, so that we can give useful initial choices.  We'll also need to do ajax lookups to get a full list of matching artifacts, as well as mount points and project names for cases like `[wiki:Baz]` or `[proj:wiki:Baz]`.

The UI could be extra nice if it didn't require typing a `[` first in some cases, since some people might not know that syntax.  If you just typed `#` it could suggest tickets and put the `[` in for you automatically if you select one.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 14 Mar 2019 02:19:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7982/</guid></item><item><title>Auto open admin sidebar</title><link>https://forge-allura.apache.org/p/allura/tickets/7972/</link><description>The new admin section in the left sidebar should be open by default if you are currently on an admin page for the tool.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 24 Aug 2015 14:28:44 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7972/</guid></item><item><title>Incorrect Content-Type on first CSS requests, causing CSS not to be used</title><link>https://forge-allura.apache.org/p/allura/tickets/7971/</link><description>I can't pull up an example right now unfortunately since it's only occasional.  I think the URLs are the ones with `_ew_` in the path.

And then if the response gets cached, then subsequent page loads still don't work either.

[#7028] was for the same issue, so see that for additional details.  That ticket just resulted in a workaround, but its not great (especially if it gets cached).  This ticket is for a real fix.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 05 Oct 2015 14:07:47 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7971/</guid></item><item><title>Need to set focus when phone validation overlay appears</title><link>https://forge-allura.apache.org/p/allura/tickets/7959/</link><description>When the phone validation overlay is enabled and shows up, we should set focus on **its** input field.  Currently the focus stays on the project name field, so your typing goes into that field which is not what you want.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 24 Aug 2015 14:29:28 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7959/</guid></item><item><title>Research odd behavior / bugs in simplemde</title><link>https://forge-allura.apache.org/p/allura/tickets/7956/</link><description>See if these are upstream bugs, report them, see if we can fix them

* when you get multiple levels deep in a list, some lines are colored green
* any sort of `foo:bar` text with a colon in it gets turned into a link style.  Should have a smarter URL pattern
* within a blockquote section, the Image button is highlighted instead of blockquote button
* `#foobar` heading without a space after #, does not get styled like a heading
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 21 Sep 2015 14:05:40 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7956/</guid></item><item><title>Add more formatting support to markdown editor</title><link>https://forge-allura.apache.org/p/allura/tickets/7955/</link><description>It'd be nice to add more toolbar buttons to support inserting formatting like:

* `~~~~` code blocks
* strikethrough
* backticks
* tables
* headers

Tables &amp; headers might need a drop-down to support choosing which one, so not sure if that is realistic.

Syntax highlighting of those elements (especially our code blocks) would be nice too, but perhaps a lot of work?

See if we can include tooltip text on the new buttons too.  I note that our custom preview and help buttons don't have tooltips.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 21 Sep 2015 14:05:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7955/</guid></item><item><title>Markdown editor should have max height</title><link>https://forge-allura.apache.org/p/allura/tickets/7950/</link><description>After a certain height, the markdown editor should switch to scrolling.  If the editor is too tall, then the toolbar is far away and it generally is just a lot bigger than normal expectations for text editing.

Method to do this: https://groups.google.com/d/msg/codemirror/1zjPxioENiA/ujiZU3Of-5oJ

With some preliminary tests, this makes [#7948] less of a problem too</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 10 Aug 2015 14:28:45 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7950/</guid></item><item><title>Better listing of files changed in a certain commit</title><link>https://forge-allura.apache.org/p/allura/tickets/7949/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 12 Apr 2016 19:33:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7949/</guid></item><item><title>Cursor position often wrong in new markdown editor</title><link>https://forge-allura.apache.org/p/allura/tickets/7948/</link><description>When editing text in the new markdown editor, the cursor can be off by a line (or few?).  This seems to happen  reliably, but exact cause is not narrowed down yet.  Seems to only be when editing existing content, not when creating new content (even pasting the exact same text).  I think it has to do with the initial height of the input area being tall.  Sometimes I can get the cursor to work properly again if I add or delete enough rows to make the textarea resize some amount.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 24 Aug 2015 14:29:42 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7948/</guid></item><item><title>Site admin search tables can overflow the page width</title><link>https://forge-allura.apache.org/p/allura/tickets/7928/</link><description>If you do a search for users and the results are really wide (e.g. super long names, emails, or having extra custom fields specified in `.ini` file) then the right-most column can be hidden.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 27 Jul 2015 14:35:12 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7928/</guid></item><item><title>Update icons</title><link>https://forge-allura.apache.org/p/allura/tickets/7924/</link><description>Our icons should be updated and support hidpi screens.  [Font awesome](http://fortawesome.github.io/Font-Awesome/) might be a good choice or possibly [fontello](http://fontello.com/).

Licenses need to be taken into consideration and included in the appropriate places.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 02 Nov 2015 15:09:18 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7924/</guid></item></channel></rss>