Bugzilla – Full Text Bug Listing
| Summary: | [connector] Best Practical Request Tracker (RT) | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Eddie Galvez <egalvez> |
| Component: | Mylyn | Assignee: | Project Inbox <mylyn-triaged> |
| Status: | CLOSED MOVED | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P4 | CC: | bloerch, brady.kimball, ebresie, m.hoffmann |
| Version: | unspecified | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| URL: | http://bestpractical.com/rt | ||
| Whiteboard: | |||
|
Description
Eddie Galvez
If there is some public version of this thing I can try to create template for generic repository connector. This system seems to be quite commonly used by tech support staff. I contacted the author a while back asking about the status of a web service API, but never got a reply. URL is: http://www.bestpractical.com/rt/ BTW, I tried web-repository plugin, but it does not work out of the box, because RT require auth before you can browse list of tickets. That may work though, when we implement auth handler as per bug 151602. I think there is no remote API. Even commandline tools operate directly on DB. Bug 151602 is resolved now. Could we hope for a web-access template for RT? (In reply to comment #4) > I think there is no remote API. Even commandline tools operate directly on DB. > Bug 151602 is resolved now. Could we hope for a web-access template for RT? I thought they had live demo web site, bit can't find it now. (In reply to comment #4) > I think there is no remote API. Even commandline tools operate directly on DB. > Bug 151602 is resolved now. Could we hope for a web-access template for RT? > This is not true. There is a nice object oriented api in perl and a REST interface. The command line utils operate vie the REST interface As a current user of RT, I am interested in helping with this ticket. Where is the information on the REST interface? (In reply to comment #7) > As a current user of RT, I am interested in helping with this ticket. > > Where is the information on the REST interface? > start here: http://wiki.bestpractical.com/view/REST Hi there, I'm currently writing an RT connector using the REST interface. So far it can do the following - Create new RT based Task Repository - Create new Query using any RT query URL and add it to the task list - Synchronizing Query seems to work Right now I try to write a Task editor though I haven't had a look yet at the editing side of the REST interface. Anyway, I want to be able to display the ticket data. There are almost no unit tests, no documentation (I do share that feature with most of the mylyn code, don't I ;-) ), much of the code needs a better error handling and presumably some refactoring, I have not considered any license related aspects (GPL, EPL, ???) yet and I'm not prepared to comply to any deadlines :-). However, if anyone is interested in sharing the workload I could imagine to put what I've got so far into some kind of public repository. Many greetings, tarek I would love to help! Just let me know when you have it hosted somewhere so I can check it out. CVS or SVN will do just fine, but I personally prefer SVN. Ok, I will check out some place for a repository. requested a mylyn-rt project on sourceforge, approval may take some days. Excellent! Could you post the link once it becomes live? Will you be doing it under EPL? > Excellent! Could you post the link once it becomes live? Will you be doing it
> under EPL?
yes and yes
Feature Update: Can open an editor now, showing in a somewhat rudimentary way
- attributes
- comments and attachments (though there is not really a difference between those in RT)
- description (which I chose to be the first text/plain comment)
- people
Saving changes not possible yet.
Right, I've just uploaded 4 plugins to sourceforge. I'm new to this so I'm not sure if you need ssh access to commit anything or if pserver with anonymous access works, too. Anyway, CVS with sourceforge is documented here: https://sourceforge.net/docman/display_doc.php?docid=29894&group_id=1 As I said in my first posting, this is really work in progress - you enter my sleeping room before I have done any hoovering. But feel free to sleep in my bed ;-) The org.oelbsk.rt plugin handles the rt connection and should not be dependent on mylyn (it is right now, I use some utility methods for http connections, but I will remove these). The other plugins are organised more or less as recommended in the mylyn wiki. And - as recommended - I took a look at the trac stuff and copied and adapted it. Ok, have fun now. If there are any problems, let me know, many greetings, tarek Please consider adding this as an entry to: http://wiki.eclipse.org/index.php/Mylyn_Extensions Done. Right, I've done some more work during the past 2 weeks. I don't think I'm going to implement many more features because first it does what I need now and second it more or less can do what RT's REST interface makes possible (though there might be murky depths yet unknown to me) ;-) The current version 0.1.0 is here: http://mylyn-rt.sourceforge.net/eclipse/update/ and I still would say it's alpha software. There are sure to be loads of bugs but I'll start using it in a real life setting and fix what I find. Of course I'll be glad to hear about bugs from others since of the variety of possible RT settings I only have access to a small subset. E. g. I did not test the connector with https or apache htaccess authentication so it's quite possible that these don't work. There might also be a lot of unnecessary error logging when the connection to the RT is broken etc. etc. RT's REST API is really weird in some places so please do expect strange behaviour especially in date and time data (they come localized through the API all from Chinese via Hebrew to Turkish and parsing them is hell). The same goes for RT's error messages, so doing a reasonable error handling based on RT's messages is hard to impossible. Anyway, here it is, have fun, greetings, tarek Thanks for posting status Tarek. Keep us posted and let us know if you have any additional needs from the API. Mylyn has been restructured, and our issue tracking has moved to GitHub [1]. We are closing ~14K Bugzilla issues to give the new team a fresh start. If you feel that this issue is still relevant, please create a new one on GitHub. [1] https://github.com/orgs/eclipse-mylyn |