https://forge-allura.apache.org/p/allura/tickets/You searched for assigned_to:"rhnvrm"enWed, 27 Dec 2017 23:40:44 -0000https://forge-allura.apache.org/p/allura/tickets/8122/As discussed previously, adding an importer for issues hosted on JIRA would ease convincing projects to use Allura. JIRA provides a method to backup issues. https://confluence.atlassian.com/adminjiracloud/exporting-issues-776636787.html The backup includes the following data: * Issues * Users and their group settings * Avatars * Attachments if selected In XML format. We already have an importer for GitHub, and the code /ForgeImporters/forgeimporters/github/tracker.py for it's ticket importer can be used for reference. I have started working on this and with the merge of this with the codebase I think would be a good time to approach Apache projects in the Incubator. Rohan VermaMon, 29 Aug 2016 15:15:36 -0000https://forge-allura.apache.org/p/allura/tickets/8122/https://forge-allura.apache.org/p/allura/tickets/8106/Recently on SF the tickets interface changed to some new UI. In this new UI, after I moderate a comment as Approved, the formatting changes and the assortment of buttons changes. But reply is not among the new buttons. I have to refresh the page before reply shows up.zeromusWed, 20 Jul 2016 18:50:00 -0000https://forge-allura.apache.org/p/allura/tickets/8106/https://forge-allura.apache.org/p/allura/tickets/8104/Sample bug: https://forge-allura.apache.org/p/allura/tickets/8103/#6b0aRohan VermaTue, 09 Aug 2016 19:15:33 -0000https://forge-allura.apache.org/p/allura/tickets/8104/https://forge-allura.apache.org/p/allura/tickets/8095/https://github.com/blog/793-introducing-the-file-finder I have currently started to implement this by searching for blobs in the root tree with matching file names. This can be extended by searching the child trees to a certain depth to find the file. This is in the patch attached below. So yesterday, I was looking to further implement this patch on the internet and was able to read the documentation of git python to use the git ls-files command and found this http://gitpython.readthedocs.io/en/stable/reference.html#git.cmd.Git But i'm not sure if this is the way to go about it since this will be limited to git repositories and I guess the previous method will be useful for all SCM repos. Also, I'm thinking that we should just expose this function via REST and use JS to display the search results instead on demand. Would like to know suggestions on how to further go about this. Rohan VermaTue, 12 Jul 2016 19:17:59 -0000https://forge-allura.apache.org/p/allura/tickets/8095/https://forge-allura.apache.org/p/allura/tickets/8093/Hello, As part of my GSoC project, I will be developing a mobile web view for Allura. I have thought about how to go about it but would love some suggestions on how to go about it. There are two ways to go about developing this: 1. Detecting it is a mobile/tablet screen and provide a different CSS file. This will be feature complete from the beginning. (Use existing templating engine) 2. Developing a seperate mobile website which we open if we detect a mobile viewport. This will not be feature complete and we will use API calls to asynchronously develop features. (Added benefit to this is that we improve the API) Rohan VermaWed, 27 Dec 2017 23:40:44 -0000https://forge-allura.apache.org/p/allura/tickets/8093/https://forge-allura.apache.org/p/allura/tickets/8092/Eg. https://forge-allura.apache.org/rest/u/brondsem/activity returns 500 This is due to line 227 since shortname attribute is not set for Profile tool. What should I do to solve it? I'm not sure what needs to be done. ~~~ 'following': data['following'], 'followee': { 'activity_name': data['followee'].shortname, 'activity_url': data['followee'].url(), 'activity_extras': {}, ~~~Rohan VermaMon, 11 Jul 2016 15:10:45 -0000https://forge-allura.apache.org/p/allura/tickets/8092/https://forge-allura.apache.org/p/allura/tickets/8090/This would make it easier for people to know that they even exist. Also, its more consistent, so you can find them when they are all closed, etc.Dave BrondsemaTue, 28 Jun 2016 14:36:10 -0000https://forge-allura.apache.org/p/allura/tickets/8090/https://forge-allura.apache.org/p/allura/tickets/8089/Hello, Since we utilize the same discussion tool between the Forum's and Tickets and Merge Requests; I want to propose that we disable pagination for tickets and merge requests and load all the comments in the ticket at once. It is a simple one line change and I have already made the change in one of my branches and would be happy to send a merge request if this is suitable. My observations are: 1. Tickets/MRs utilize a lot of shared information that might be useful to scroll through. 2. Due to pagination being less friendly to Search Engines, content inside issues often do not show up on search resulting in duplicate tickets being made. 3. Similarly, duplication of comments might also take place, say for example during the resolution of a ticket some user points out some information in page 2 but the new user reading it might post the same information without having to reach page 2.Rohan VermaMon, 06 Jun 2016 15:11:33 -0000https://forge-allura.apache.org/p/allura/tickets/8089/https://forge-allura.apache.org/p/allura/tickets/8088/Hello, after various iterations of the designs I think this one is the best option that matches the current design of the forge. In this design, I have added a toolbar inside the header so that all the information and actions relating to a comment are isolated inside that specific bubble. Also, hopefully the indentation between replies is more intuitive now. I have added two screenshots, one having more pronounced buttons and one having sleeker buttons. Please give feedback and suggest further changes. Source tree: https://forge-allura.apache.org/u/rhnvrm/allura/ci/rhnvrm/discussion/style-changes/~/tree/Rohan VermaWed, 13 Jul 2016 19:29:58 -0000https://forge-allura.apache.org/p/allura/tickets/8088/https://forge-allura.apache.org/p/allura/tickets/8087/ Rohan VermaTue, 24 May 2016 15:11:31 -0000https://forge-allura.apache.org/p/allura/tickets/8087/https://forge-allura.apache.org/p/allura/tickets/8086/This was requested in the IRC by fortpedro. For example after searcing for https://forge-allura.apache.org/p/allura/tickets/search/?q=labels:%22bitesize%22 There could be a button that lets you add the option of open/closed tickets. Rohan VermaThu, 19 May 2016 21:24:23 -0000https://forge-allura.apache.org/p/allura/tickets/8086/https://forge-allura.apache.org/p/allura/tickets/8077/I was experimenting with the API on https://jsfiddle.net/r4jg82fr/ and found that it would be useful to supply the profile photo url in the response(eg https://forge-allura.apache.org/rest/p/allura/tickets/_discuss/thread/2abc9fd7/) along with each post. Since, getting it via another ajax such as https://forge-allura.apache.org/rest/u/brondsem call would be expensive. Also, users who have set the image to be fetched from gravatar have it set to null. (eg. https://forge-allura.apache.org/rest/u/rhnvrm)Rohan VermaMon, 23 May 2016 19:07:22 -0000https://forge-allura.apache.org/p/allura/tickets/8077/https://forge-allura.apache.org/p/allura/tickets/8072/On merge requests, it always says "$USER asked you to merge ....". The word "you" only makes sense if you have access to merge the request, we shouldn't show it to everyone else (including the contributor). Pick a different phrase that works better for everyone.Dave BrondsemaWed, 06 Apr 2016 19:33:31 -0000https://forge-allura.apache.org/p/allura/tickets/8072/https://forge-allura.apache.org/p/allura/tickets/7965/ Our rest api endpoints for git/hg/svn need to be cleaned up. Currently they are too simplistic (svn isn't even hooked up). Our RAML api documentation should be updated as well. It might be easier to update the RAML first to ensure a consistant and reusable interface that can then be implemented in code.Heith SeewaldFri, 20 May 2016 21:04:45 -0000https://forge-allura.apache.org/p/allura/tickets/7965/https://forge-allura.apache.org/p/allura/tickets/7682/Awards and award grants on /p/_admin/accolades can be deleted without any confirmation, which is a bit dangerous. We should add a confirmation.Dave BrondsemaWed, 23 Mar 2016 19:20:27 -0000https://forge-allura.apache.org/p/allura/tickets/7682/https://forge-allura.apache.org/p/allura/tickets/7145/We should run a background task instead of calling it inline, so that there's not an error when solr's down. And makes the operation faster for the user anyway. See also [#4799] which is somewhat of a reverse problem ~~~~ File '/var/local/allura/Allura/allura/app.py', line 474 in uninstall project_id, self.config.options['mount_point'])) File '/var/local/allura/Allura/allura/lib/solr.py', line 76 in delete responses.append(solr.delete(*args, **kw)) File '/var/local/env-allura/lib/python2.7/site-packages/TimerMiddleware-0.4.4-py2.7.egg/timermiddleware/__init__.py', line 117 in wrapper return self.run_and_log(func, inst, *args, **kwargs) File '/var/local/env-allura/lib/python2.7/site-packages/TimerMiddleware-0.4.4-py2.7.egg/timermiddleware/__init__.py', line 126 in run_and_log return func(*args, **kwargs) File '/var/local/env-allura/lib/python2.7/site-packages/pysolr-2.1.0_beta-py2.7.egg/pysolr.py', line 716 in delete response = self._update(m, commit=commit, waitFlush=waitFlush, waitSearcher=waitSearcher) File '/var/local/env-allura/lib/python2.7/site-packages/pysolr-2.1.0_beta-py2.7.egg/pysolr.py', line 401 in _update return self._send_request('POST', path, message, {'Content-type': 'text/xml; charset=utf-8'}) File '/var/local/env-allura/lib/python2.7/site-packages/pysolr-2.1.0_beta-py2.7.egg/pysolr.py', line 310 in _send_request headers, response = http.request(url, method=method, body=body, headers=headers) File '/var/local/env-allura/lib/python2.7/site-packages/httplib2-0.7.4-py2.7.egg/httplib2/__init__.py', line 1544 in request (response, content) = self._request(conn, authority, uri, request_uri, method, body, headers, redirections, cachekey) File '/var/local/env-allura/lib/python2.7/site-packages/httplib2-0.7.4-py2.7.egg/httplib2/__init__.py', line 1294 in _request (response, content) = self._conn_request(conn, request_uri, method, body, headers) File '/var/local/env-allura/lib/python2.7/site-packages/httplib2-0.7.4-py2.7.egg/httplib2/__init__.py', line 1230 in _conn_request conn.connect() File '/var/local/env-allura/lib/python2.7/site-packages/httplib2-0.7.4-py2.7.egg/httplib2/__init__.py', line 890 in connect raise socket.error, msg ~~~~Dave BrondsemaMon, 04 Apr 2016 19:45:05 -0000https://forge-allura.apache.org/p/allura/tickets/7145/https://forge-allura.apache.org/p/allura/tickets/6581/When creating a new Merge Request, the list of commits that will be included should be shown so that the user can verify that they are choosing the correct source & target branch. The list should update if the source or target branches are changed.Cory JohnsThu, 07 Jul 2016 20:46:44 -0000https://forge-allura.apache.org/p/allura/tickets/6581/