<?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:"shalithasuranga"</description><language>en</language><lastBuildDate>Fri, 04 Oct 2019 21:42:55 -0000</lastBuildDate><item><title>gsoc19 - d1 - Writing documentation for user mentions feature</title><link>https://forge-allura.apache.org/p/allura/tickets/8324/</link><description>- Updating in-app formatting guide with the new feature.
- Updating features [page](https://forge-allura.apache.org/p/allura/wiki/Features/). 
- Writing a blog post about new feature in Allura blog. Eg: http://allura.apache.org/posts/2016-gsoc-16.html
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Fri, 04 Oct 2019 21:42:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8324/</guid></item><item><title>gsoc19 - Trigger notification task per each artifact creation/modification and add tests</title><link>https://forge-allura.apache.org/p/allura/tickets/8323/</link><description>Add a test for the send_usermentions_notification task. Also.. `send_usermentions_notification` task is only called in a few places so far, but would be good to do in all the places where a new artifact is created/modified(content) (new wiki page, new ticket, new blog post, new merge request). Maybe a new ticket for all that together.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Fri, 04 Oct 2019 21:42:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8323/</guid></item><item><title>Higher resolution icons in user card</title><link>https://forge-allura.apache.org/p/allura/tickets/8304/</link><description>The user card uses an image with src of `/u/myusername/user_icon` when using user icons uploaded into Allura (I haven't checked out exactly what happens with gravatar icons) and those default to 48x48 for legacy reasons.  We should use the `w` parameters of the icon macros/urls to get a 64x64 image or maybe even 128x128 for hi-dpi screens.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 15 Jul 2019 15:27:46 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8304/</guid></item><item><title>More precise markdown @username regex</title><link>https://forge-allura.apache.org/p/allura/tickets/8299/</link><description>If there exists a user with username "foo" and some markdown content has johndoe@foo.com then we'll incorrectly get a username link of @foo in the middle of that email address.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 15 Jul 2019 15:27:46 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8299/</guid></item><item><title>gsoc19-c5: Add an area for user mentions notifications</title><link>https://forge-allura.apache.org/p/allura/tickets/8285/</link><description>*Todo*

An option to turn on/off notifications for user mentions to be added to the subscriptions tab. An endpoint can be implemented to save the user setting for sending notifications. 

*What is expected*

Allura user can turn on/off user mention notifications. If the user has disabled the setting, notification emails will not  be sent.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Fri, 04 Oct 2019 21:42:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8285/</guid></item><item><title>gsoc19-c4: Implement the notification email sender</title><link>https://forge-allura.apache.org/p/allura/tickets/8284/</link><description>*Todo*

This function is responsible for detecting user mentions and sending email notifications. For the detection markdown extenstion can be reused. For sending emails existing interfaces can be used; or any other better mechanism will be discussed before the implementation.

*What is expected*

When a user is mentioned (and the markdown is saved) the relevant user will be notified with an email 

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Fri, 04 Oct 2019 21:42:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8284/</guid></item><item><title>gsoc19-c3: Adding infotip for user mentions</title><link>https://forge-allura.apache.org/p/allura/tickets/8283/</link><description>*Todo* 

When user hovers the mouse cursor on a link which mentions a user, info-tip can be displayed. User information such as username, display name, profile avatar, location, profile summary and availability can be display in the tooltip.

Another third party plugin or existing JQuery tooltipster plugin can be used. Moreover, this tooltip can be added to areas such as tickets, activity, etc where usernames are displayed with a hyperlink. 

*What is expected*

Working info tip on user mentions of markdown rendered text and in other places as well</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Mon, 15 Jul 2019 15:27:46 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8283/</guid></item><item><title>gsoc19-c2: Implement  audocomplete list to selected users for mentioning</title><link>https://forge-allura.apache.org/p/allura/tickets/8282/</link><description>*Todo*

The show-hit addon of CodeMirror library can be used. User data array can be populated with an API endpoint. Autocomplete list can be triggered with @ character.

*What is expected*

Allura user can hit "@" character and get the autocomplete list to select a user for mentioning. once an user is selected from the autocomplete list, the username will be added with "@" Eg:- @admin1
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Mon, 17 Jun 2019 15:19:15 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8282/</guid></item><item><title>gsoc19-c1: Enable user mentions in markdown editor</title><link>https://forge-allura.apache.org/p/allura/tickets/8281/</link><description>*Todo*

A new extension can be created by extending `markdown.Extension` class of the python markdown library. Also, the link-replacement logic can be implemented by extending `markdown.inlinepatterns.Pattern` class.

*What is expected*

User mentions such as @admin1 @user1 will be converted into hyperlinks when markdown is rendered as HTML.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Mon, 17 Jun 2019 15:19:15 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8281/</guid></item><item><title>Indicate current reaction of comment</title><link>https://forge-allura.apache.org/p/allura/tickets/8263/</link><description>Currently when user already reacted to a specific comment it is not indicated to the user.  There are several ways of doing that. We can highlight already reacted emoji or otherwise we can display a tooltip for reaction stats like Github does.

Your ideas?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Mon, 17 Jun 2019 15:19:14 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8263/</guid></item><item><title>Adding reaction support for comments</title><link>https://forge-allura.apache.org/p/allura/tickets/8253/</link><description>This is related with merge request [#135](https://forge-allura.apache.org/p/allura/git/merge-requests/135/) comments. 

VotableArtifact stores +1 and -1 in seperate fields 
```
    votes_up = FieldProperty(int, if_missing=0)
    votes_down = FieldProperty(int, if_missing=0)
```

So can we create something like ReactableArtifact

```
    react_thumbs_up = FieldProperty(int, if_missing=0)
    react_thumbs_down = FieldProperty(int, if_missing=0)
    react_thumbs_tada = FieldProperty(int, if_missing=0)
    ....
    ..
    react_thumbs_up_users = FieldProperty(int, if_missing=0)
```

Another thing is that since Allura supports comment replies like a tree. we may ignore who reacted .. we just take count only. But normally it is needed</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Mon, 17 Jun 2019 15:19:13 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8253/</guid></item><item><title>When deleting module and user at permissions page still gives 404</title><link>https://forge-allura.apache.org/p/allura/tickets/8242/</link><description>We have fixed 404 issue. it will redirect to root of project if user deletes module from project/modulename/....../../
but permission endpoint is diffent than this it is project/admin/modulename/.....
So this cause an error

We need to update regex

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8242/</guid></item><item><title>Screenshots lightbox</title><link>https://forge-allura.apache.org/p/allura/tickets/8239/</link><description>Project admin screenshots section can manage screenshots per  each project. Whereas how user can display them to outside? Is there an existing method

Can we instroduce a shortcode or something for wikis or any other option .. Please advice</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8239/</guid></item><item><title>Add "title" to envelope icon</title><link>https://forge-allura.apache.org/p/allura/tickets/8233/</link><description>The envelope icon on wiki pages (in upper right dark bar) does not have title text like other icons do, so you can't hover over it to find out what it does.  We should add helpful title text.  Similarly for the envelope icon when it is used other places too, like tickets, etc.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8233/</guid></item><item><title>Make checklists interactive</title><link>https://forge-allura.apache.org/p/allura/tickets/8230/</link><description>It would be nice if the new checklists from [#8085] were interactive too for people that have edit access.  The markdown-checklist package has some helper JS for it, but would take custom code to handle the ajax and do the update.  Maybe use existing rest APIs for some artifact types, but everything (wiki page, ticket, blog post, comment, etc) will need to be handled specifically to hit the right endpoint and with the right data format.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:20 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8230/</guid></item><item><title>Component delete everything end up with 404</title><link>https://forge-allura.apache.org/p/allura/tickets/8225/</link><description>**Step to reproduce **

Select wiki, ticket or forum -&gt; Delete everything

Then user will be redirected to **404 - We're sorry but we weren't able to process this request.**

Can we redirect to project root page instead? Your ideas 
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Shalitha Suranga</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:20 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8225/</guid></item><item><title>Add support for checkboxes to the markdown convertor</title><link>https://forge-allura.apache.org/p/allura/tickets/8085/</link><description>Checkboxes can be rendered from [ ] and [x]

It is useful for maintaining lists and TODOs</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rohan Verma</dc:creator><pubDate>Mon, 24 Sep 2018 19:36:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8085/</guid></item><item><title>Subscriptions page should have the issues' Title column NEEDS MIGRATION</title><link>https://forge-allura.apache.org/p/allura/tickets/8081/</link><description>The subscriptions page on the account preferences currently lists 4 columns: project, tool, item and the check option.
The item number doesn't tell much. In order to make it useful, I think that you should add also a column with the title of the issue. There's a lot of padding between each column now. If the title is too long, it should be wrapped at a fixed maximum length.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Federico Bruni</dc:creator><pubDate>Tue, 30 Oct 2018 20:36:25 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8081/</guid></item><item><title>Animated gif attachment silently converted to static gif</title><link>https://forge-allura.apache.org/p/allura/tickets/8043/</link><description>[forge:site-support:#11626]

https://sourceforge.net/p/forge/site-support/11626/

---

When I tried to upload an animated gif, see here: http://img.xrmb2.net/images/703616.gif sourceforge, without any warning or so converts this to a static image which is only 7.1KB instead of 26.6KB. Compare the attachment (I'm really uploading the same gif, not a static one, I checked thrice).

----

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John Barrett</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:19 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8043/</guid></item><item><title>Show password requirements on forms</title><link>https://forge-allura.apache.org/p/allura/tickets/7459/</link><description>It would be helpful to show password requirements (aka min # of chars) on the password change form.  And account creation.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:19 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7459/</guid></item><item><title>Handle github emoji</title><link>https://forge-allura.apache.org/p/allura/tickets/6923/</link><description>Emoji (e.g. :+1: thumbs up) are heavily used on some GH projects and would be good to carry over during import. However, the images are not licensed for us to redistribute https://github.com/github/gemoji/blob/master/LICENSE  Maybe we could use https://github.com/Genshin/PhantomOpenEmoji if the mapping is straightforward.  We also need to decide if we want an emoji-like feature throughout our markdown or handle this just at import.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:19 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6923/</guid></item><item><title>if same filename used, screenshot thumbnail not update [ss4951]</title><link>https://forge-allura.apache.org/p/allura/tickets/6560/</link><description>[forge:site-support:#4951]

See https://sourceforge.net/p/tbmailsplit/admin/screenshots

If you click through to the full screenshots, those are properly updated, but the thumbnails are the older versions.

The user says he used the same filename when updating the new image (but locally stored in different folders).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:19 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6560/</guid></item><item><title>Uploaded BMP and didn't get an error [21047]</title><link>https://forge-allura.apache.org/p/allura/tickets/2578/</link><description>https://sourceforge.net/apps/trac/sourceforge/ticket/21047

&gt;I uploaded a bmp file as a screen shot. When I uploaded it, it didn't do anything, and never gave me an error.

&gt;I think you should specify the acceptable file formats somewhere on the upload site, or have a filter on the open file dialog to choose the file to upload.

He uploaded via Admin -&gt; Screenshots on an allura project.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Tue, 30 Oct 2018 14:21:18 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/2578/</guid></item></channel></rss>